User interfaces for transactions

专利摘要:
The present disclosure generally relates to transaction user interfaces. In some examples, a user is notified if there is an error with transaction parameters and the device determines whether potentially compatible transaction parameters are available on the electronic device. In some examples, the user is notified if there is an error with transaction parameters and the user is prompted to use another device to enter new transaction information.
公开号:DK201670622A1
申请号:DKP201670622
申请日:2016-08-16
公开日:2018-02-12
发明作者:Marcel Van Os
申请人:Apple Inc；
IPC主号:

专利说明:

<¹θ> DANMARK <¹°> DK 2016 70622 A1
<¹²> PATENTANSØGNING
Patent- og
Varemærkestyrelsen (51)
Int.CI.: G 06 Q 20/40 (2012.01)
G 06 F 3/0484(2013.01) G 06 Q 20/42 (2012.01)
G 04 G 21/08 (2010.01) G 06 Q 20/12 (2012.01)
G 06 F 3/0481 (2013.01) G 06 Q 20/32 (2012.01) (21) Ansøgningsnummer: PA 2016 70622 (22) Indleveringsdato: 2016-08-16 (24) Løbedag: 2016-08-16 (41) Aim. tilgængelig: 2017-12-13 (30) Prioritet: 2016-06-12 US 62/349,010 (71) Ansøger: Apple Inc., 1 Infinite Loop, Cupertino, 95014 California, USA (72) Opfinder: Marcel Van Os, c/o Apple Inc., 1 Infinite Loop, Cupertino, 95014 CA California, USA (74) Fuldmægtig: Zacco Denmark A/S, Arne Jacobsens Allé 15, 2300 København S, Danmark (54) Benævnelse: User interfaces for transactions (56) Fremdragne publikationer:
US 2016/0034887 A1 US 2015/0242837 A1 US 2015/0229750 A1 US 2015/0195133 A1 US 2012/0024947 A1 US 2016/0086176 A1 US 2015/0120545 A1 US 2015/0012435 A1 US 2014/0372309 A1 US 7,454,192 B1 US 2016/0012417 A1 US 2011/0106671 A1 US 2011/0214158 A1 US 2016/0132864 A1 WO 2015/0062410 A1 (57) Sammendrag:
The present disclosure generally relates to transaction user interfaces. In some examples, a user is notified if there is an error with transaction parameters and the device determines whether potentially compatible transaction parameters are available on the electronic device. In some examples, the user is notified if there is an error with transaction parameters and the user is prompted to use another device to enter new transaction information.
Fortsættes ...
DK 2016 70622 A1
DK 2016 70622 A1
USER INTERFACES FOR TRANSACTION’S
CROSS-REFERENCE TO RELATED APPLICATIONS (0001( This application claims priority to the following co-pending provisional applications; U.S. Patent Application Serial No. 62/349.010, entitled “USER INTERFACES FOR TRANSACTIONS”, filed June 12, 2016, which is hereby incoiporated by reference in its entirety.
FIELD (00021 The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing transactions.
BACKGROUND (00031 The use of electronic devices for participating in transactions has increased significantly in recent years. Exemplary techniques for participating in transactions include making an online purchase ofa good or service on a website. Participating in transactions using such traditional techniques often requires the user to manually enter information, such as account information and personal information, using insecure and slow methods.
BRIEF SUMMARY (0004( Some techniques for managing transactions using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interlace, which may include multiple key presses or keystrokes, even at a reduced-size electronic device, such as a smartwatch, Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration, is particularly important in battery-operated devices. For another example, some existing techniques require the user to manually enter extensive information at the device to be used for the transaction, such as on a smartwatch. This can be inefficient when other devices with enhanced input mechanism, such as a smart phone or laptop, are available.
DK 2016 70622 A1 {ΘΘΘ5| Accordingly, the present techniques provide electronic devices with fester, nrøre efficient, and more secure methods and interfeces for managing transactions. Such methods and interfaces optionally complement or replace other methods for managing transactions. Such methods aud interfaces reduce the cognitive burden on a user and produce a nrøre efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. Further, such methods and interfaces reduce the amount of input required a t electronic devices, such as smartwatches.
|O006] In accordance with some embodiments, a method performed at an electronic device with a display, one or more input devices, and a hardware button is described. The method comprises; displaying, on the display, an application user intertaee for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity associated with the respective application; while displaying the application user interface, detecting, via the one or more input devices, selection of the transaction affordance; and in response to detecting selection of the transaction affordance, displaying a transaction user interface that includes concurrently displaying: transaction details for the acti vity associated with the respective application; and instructions to activate the hardware button of the device to authorize payment for the activity associated with the respective application.
|'0007J In accordance with some embodiments, a. non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, one or more input devices, and a hardware button. The one ot more programs including instructions for: displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity associated with the respective application; while displaying the application user interlace, detecting, via the one or more input devices, selection of the transaction affordance; and in response to detecting selection of the transaction affordance, displaying a transaction user intertaee that includes concurrently displaying; transaction details for the activity associated with the respective application; and instructions to activate the hardware button of the device to authorize payment for the activity associated with the respective application.
DK 2016 70622 A1 [ΘΘΘ8 j In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured, to be executed by one or more processors of an electronic device with a display, one or more input devices, and a hardware button. The one or more programs including instructions for.' displaying,, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity associated with the respective application; while displaying the application user interface, detecting, via the one or more input devices, selection of the transaction a.f&rdance; and in response to detecting selection of the transaction affordance, displaying a transaction, user interface that includes concurrently displaying: transaction details for the activity associated with the respective application; and instructions to activate the hardware button of the device to authorize payment for the activity associated with, the respective application.
jtKKfo] In accordance with some embodiments, an electronic device is described. The electronic device comprises; a display; one or mote input devices; a hardware button; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for; displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity associated with the respective application; while displaying the application user interface, detecting, via the one or more input devices, selection of the transaction affordance; and in response to detecting selection of the transaction affordance, displaying a transaction user interface that includes concurrently displaying; transaction details for the activity associated with the respective application; and instructions to activate the hardware button of the device to authorize payment for the activity associated with the respective application.
looio] In accordance with some embodiments, an electronic device is described. The electronic device comprising: a display; one or more input devices; a hardware button; means for displaying, on the display, an application user interface for a respective application, wherein the application user interlace includes a. transaction affordance for requesting payment for activity associated with the respective application.; means, while displaying the application user interface.
DK 2016 70622 A1 for detecting, via the one or more input devices, selection of the transaction affordance; and means, responsive to detecting selection of the transaction affordance, for displaying a transaction user interlace that includes concurrently displaying; transaction details for the activity associated with the respective application; and instructions to activate the hardware button of the device to authorize payment for the activi ty associated with the respective application.
[0011] in accordance with some embodimeuts. a method performed at an electronic device with a display and one or more input devices is described. The method comprises: receiving a request to proceed with a transaction using transaction parameters; in response to the request to proceed with the transaction. In accordance with a determination. that there is an error with the transaction parameters, displaying an error notification indicating that an error has been detected; receiving, via the one or more input de vices, a request to correct the error; and in response to receiving the request to correct the error: in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on the display, one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
(0012] In accordance with some embodiments, a non-tTansitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more input devices, the one or more programs including instructions for: receiving a request to proceed with a transaction using transaction parameters; in response to the request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters, displaying an error notification indicating that an error has been detected; recei ving, via the one or more input devices, a request to correct the error; and in response to receiving the request to correct the error: in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on the display , one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not
DK 2016 70622 A1 available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
(0013] In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more input devices, the one or more programs including instructions for: receiving a request to proceed with a transaction using transaction parameters; in response to the request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters, displaying an error notification indicating that an. error has been detected; receiving, via the one or more input devices, a request to correct the error; and in response to receiving the request to correct the error: in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on the display, one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
(0014( In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or mote input devices; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or .more programs including instructions tor: receiving a request to proceed with a transaction using transaction parameters; in response to tire request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters, displaying an error notification indicating that an error has been detected; receiving, via the one or more input devices, a request to correct the error; and in response to receiving the request to correct, the error; in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on fire display, one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
DK 2016 70622 A1 fOOISj hi accordance with some embodiments, an electronic device is described, The electronic device comprises; a display; one or more input devices; means for receiving a request to proceed with a transaction using transaction parameters; means, responsive to the request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters, for displaying an error notification indicating that an error has been detected; means for receiving, via the one or more input devices, a request to correct the error; and means, responsive to receiving the request to correct the error, for; in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on the display, one or more of the potentially compatible transaction parameters: and in accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
jwiq In accordance with some embodiments, an electronic device is described. The electronic· device comprises: a display unit; one or more input device units; a hardware button unit; and a processing unit coupled to the display unit, the one or more input device units, and the hardware button unit, the processing unit configured to: enable display, on the display unit, of an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity associated with the respective application; while enabling display of the application user interface, detect, via the one or more input device units, selection of the transaction affordance; and in response to detectmg selection of the transaction affordance, enable display, on the display unit, of a transaction user interface that includes concurrently displaying; transaction details for the activity associated with the respective application; and instructions to activate the hardware button unit of the electronic device to a uthorize payment for the acti vity associated with the respective application, | ÖÖI7 j In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display unit; one or more input device units; and a processing unit coupled to the display unit and the one or more input device units, the processing unit configured to: recei ve a request to proceed with a transaction using transaction parameters; in response to
DK 2016 70622 A1 the request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters, enable display, on the display unit, of an error notification indicating that an error has been detected; recei ve, via the one or more input device units, a request to correct the error; and in response to receiving the request to correct the error: in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, enable display, on fhe display unit, of one or mom of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the electronic device, enable display, on the display unit, of instructions to enter additional transaction parameters on a companion device that is different from the electronic device, (0018] Executable instructions lor performing these functions are optional is. included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
(9019] Thus, devices are provided with faster, more efficient methods and interfaces for managing transactions, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interlaces may complement or replace other methods for managing transactions.
DESCRIPTION OF THE FIGURES (0020] For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
(0021 j FIG. 1A is a block diagram illustrating a portable multifunction dev ice w ith a touchsensitive display in accordance with some embodiments.
(0022] FIG. 1B is a block diagram illustrating exemplars components for event handling in accordance with some embodiments.
J
DK 2016 70622 A1 (0023J FIG. 2 illustrates a -portable multifunction device having a touch screen in accordance with some embodiments.
(0024( FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.
(0025 j FIG, 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some erabodimeuis.
(0026( FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate trom the display in accordance with some embodiments.
(0027( FIG. 5 A illustrates a personal electronic device in accordance with some embodiments.
(0028( FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.
(0020( FIGS. 5C-5D illustrate exemplary components of a personal electronic device having a touch-sensitive display and intensity sensors in accordance with some embodiments.
(0030( FIGS. 5E-5H illustrate exemplary' components and user interfeces of a personal electronic device in accordance with some embodiments.
(0031( FIG, 6 illustrates exemplary devices connected via one or more communication channels to complete participate in a transaction .in accordance with some embodiments.
(0032J FIGS. 7A-7O illustrate exemplary user interfaces for managing transactions, in accordance with some embodiments.
(0033( FIG. S is a flow diagram illustrating a method for managing transactions, in accordance with some embodiments.
(0034( FIGS. 9A-9N illustrate exemplary user interfaces for managing transactions, in accordance with some embodiments.
DK 2016 70622 A1 (0035] FIG, 10 is a flow diagram illustrating a method for managing transactions, in accordance with some embodiments.
(0Ö36] FIGS. 11-12 are functional block diagrams, in accordance with some embodiments.
DESCRIPTION OF EMBODIMENTS (0037( The following description sets forth exemplary methods, parameters, and the like, it should be recognized, however, that, such description is not intended as a 1 imitation on. the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
(0038( There is a need fot eieettome devces that provide efficient methods and interfaces for managing tiansactions in accordance wtth some embodiments, the user is notified if there Is an error with transaction parameters and the device determines whether potentially compatible transaction parameters are available on the eieetronie device. In accordance with some embodiments, the user is notified if there is an error with transaction parameters and the user is prompted to use another device to enter new transaction information. Such techniques can reduce the cognitive burden on a user participates in transactions, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs, (0030( Below, FIGS, I A~1B, 2, 3, 4A-4B, and 5A-5H provide a description of exemplary devices for performing the techniques for managing event notifications. FIG. 6 illustrates exemplary devices connected via one or more communication channels to complete participate in a transaction in accordance with some embodiments. FIGS, 7A-7O illustrate exemplary user interfaces for managing transactions, FIG. 8 is a flow diagram illustrating methods of managing transactions in accordance with some embodiments. The user interfaces in FIGS. 7A-7O are used to illustrate the processes described below, including the processes in FIG. 8. FIGS. 9A-9N Illustrate exemplary user interfeces for managing transactions. FIG, 10 is a flow diagram illustrating methods of managing transactions in accordance with some embodiments. The user interlaces in FIGS. 9A-9N are used io illustrate the processes described below, including the processes in FIG, 10.
DK 2016 70622 A1 |0040j Although the following description uses terms “fitst,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms ate only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
(0041] The terminology used in the description ofthe various described embodiments herein is for the purpose o.f describing particular embodiments only and is not intended to be limiting. As used in the description ofthe various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes“including,” “comprises,” and/or “comprising ” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof (0042j The term “if’ is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
[ΘΘ43] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc, of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used.
DK 2016 70622 A1 li should also be understood thai, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g,, a touch screen display and/or a touchpad), i0044j In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
|ÖÖ4SJ The device typically supports a variety·' of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-tnail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
|ÖÖ46| The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on tire device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application, hi this way, a common physical architecture (such as tire touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
|0O47j Attention is now directed toward embodiments of portable devices with touchsensitive displays. FIG. 1A is a block-diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system,·” Device 100 includes memory 102 (which optionally·' includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry·' 110, speaker III, microphone 113, inputfoutput (I/O) subsystem 106, other input control devices 116,
DK 2016 70622 A1 and external -port 124. Device 100 optionally includes one or more optical sensors 164, Device 100 optionally includes one or more contact intensity sensors 165 lor detecting intensity of contacts on device 100 (e.g., a touch-sensitive surfece such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 1.67 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensiti ve display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.
[0048] As used in the specification and claims, the term “intensity” of a contact on a touchsensitive surface refers fo the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally , determined (or measured ) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to fhe toach-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface, in some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure ofthe stylus on the touch-sensitive surfe.ee. Alternatively, the size ofthe contact area detected on the toueh-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surfece proximate to the confect and/or changes thereto, and/or the resistance ofthe touch-sensitive surfece proximate to the confect and/or changes thereto are, optionally, used as a substitute for the force or pressure ofthe contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g,, the intensity threshold is a pressure threshold measured in units of pressure). Using the in tensity of a contact as an attribute of a user input
DK 2016 70622 A1 allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touchsensitive surface, or a physicaVmechanical control such as a knob or a button).
[ΘΘ49] As used in the specification and claims, the term ‘tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g,, bousing) of fhe device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user’s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user’s hand), the tactile output generated by fhe physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device.
For example, movement of a touch-sensitive surface (e.g,, a touch-sensitive display or trackpad) is, optional ly, interpreted by the user as a “down click” or “op click” of a physical actuator button, in some cases, a user will feel a tactile sensation such as an down click” or up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g,, displaced) by the user’s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensiti ve surface. While such interpretations of touch by a user will he subject to the individualized sensory perceptions of the user, diere are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that wi ll generate the described sensory perception for a typical (or average) user.
JOOSO) It should be appreciated that de ice 1 Oi.) is only one example of a portable multifunction device, and that device ItiO optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or
DK 2016 70622 A1 arrangement of the components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits.
|0051 j Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
|Ö0S2j Peripherals interface 118 can be used to couple input and output peripherals ofthe device to CPU 120 and memory' 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perten various functions for device 100 and to process data. .In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
|00S3j RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices bv wireless communication. The RF circuitry 108 optionally Includes well-known circuitry’ for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including hut not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV14
DK 2016 70622 A1
DO), HSPA, HSPA-L Dual-Cell HSPA (DC-HSFDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g, IEEE 802,11 a, IEEE 802.1 lb, IEEE 802.1 Ig, IEEE 802.1 in, and/or IEEE 802.1 lac), voice over Internet Protocol (VoIP), Wi-ΜΑΧ, a protocol for e-mail (e.g, Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g, extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
|P054j Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111, Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 1.10 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry .108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g, 212, PIG. 2). The headset jack provides an interlace between audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g, a headphone for one or both ears) and input (e.g, a microphone).
|'0055) I/O subsystem 106 couples input/output peripherals on device 100. such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, anti one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g, push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click
DK 2016 70622 A1 wheels, and so ferlh. in some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following; a keyboard, an infrared, port, a USB port, and a pointer device such as a mouse, The one or more buttons (e.g., 208, FIG. 2) optionally include an up/down button, for volume control of speaker 111 and/or microphone 1.13. The one or more buttons optionally include a push button (e.g,, 206, FIG. 2).
|0056j A quick press ofthe push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the de see, as described in U.S. Patent Application 11/322,549, “Unlocking a Device by Performing Gestütes on an Unlock Image,” filed December 23, 2005, U.S. Pat. No, 7,657,849, which is hereby incorporated by reference in its entirety. A longer press ofthe push button (e.g., 206) optionally turns power to device .100 on or off. The functionality of one or more ofthe buttons are. optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
(0057] Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen .112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”), in some embodiments, some or ail ofthe visual output optionally corresponds to user-interlace objects.
£005$] Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact Touch screen 1.12 and display controller 156 (along with any associated modules and/or sets of instructions in. memory 102) detect contact (and any movement or breaking ofthe contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft, keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
1ÖÖS9] Touch screen 112 optionally uses LCD (hquid crystal display} technology. LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other
DK 2016 70622 A1 display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and. any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including hut not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements lor determining one or more points of contact with touch screen 112. In. an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
|0060| A touch-sensitive display in some embodiments of touch screen 1.1.2 is, optionally', analogous to the multi-touch sensitive touchpads described in the following U.S. Patents: 6,323,846 (Westerman et. al.), 6,570,557 (Westerman et al,), and/or 6,677,932 (Westerman), and/or U.S, Patent Publication 2002/0015024.41, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. Patent Application No. 11/381,313, “Multipoint Touch Surface Controller,’’ filed May 2, 2006; (2) U.S. Patent Application No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) US, Patent Application No. 10/903,964, “Gestures For Touch Sensitive input Devices,” filed July 30, 2004; (4) U.S. Patent Application No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed January 31, 2005; (5) U.S. Patent Application No. 11 /038,590, “Mode-Based Graphical User Interlaces For Touch Sensitive input Devices,” filed January 18, 2005; (6) U.S, Patent Application No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed September 16, 2005; (7) US. Patent Application No. 11/228,700, “Operation Of A Computer With .A Touch Screen Interface,” filed September 16, 2005; (8) ITS. Patent .Application No. 11/228,737, “Activating Virtual Keys Of .A Touch-Screen Virtual Keyboard,” filed September 16, 2005; and (9) US. Patent Application No. 11/367,749, “Multi-Functional Hand-Held Device,” filed March 3, 2006. All of these applications are incorporated by reference herein in their entirety.
|O062 j Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user
DK 2016 70622 A1 optionally makes contact with touch screen I12 using any suitable object or appendage, such as a stylus, a finger, and so forth, in some embodiments, the user interlace is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
(0063] In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad, is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen, (0064] Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a. power management system, one or more power sources (e.g,, battery, alternating current (AC)), a recharging system, a power foilure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
[ΘΘ65] Device 100 optionally also includes one or more optical sensors 164 FIG. I A shows an optical sensor coupled to optical sensor controller 158 in rø subsystem 106, Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light Sam the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user’s image is, optionally, obtained for video conferencing while the user views the other
DK 2016 70622 A1 video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating the Sens and the sensor in the device housing) so that a single optical sensor 164 is used along with the touch screen display for 'both video conferencing and still and/or video image acquisition.
(0066] Device 100 optionally also includes one or more contact intensity sensors 165.
FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity' sensor .165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touchsensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.
(0067( Device 100 optionally also includes one or more proximity sensors 166. FIG. IA shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 is, optionally, coupled to input controller 160 in FÖ subsystem 106. Proximity sensor 166 optionally performs as described in U.S. Patent Application Nos, 11/241,839, “Proximity Detector In Handheld Device”; 11/240,788, “Proximity' Detector In Handheld Device“;
11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby· incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user’s ear (e.g., when the user is making a phone call).
(0068] Device 100 optionally' also includes one or more tactile output generators 167.
FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in ΙΌ
DK 2016 70622 A1 subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or oilier tactile output generating component (e.g,, a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that, are capable of being sensed by a user of device 100. In some embodiments, at least, one tactile output generator is collocated with, or proximate to, a. touchsensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile ou tput, by moving the touch-sensitive surface vertically (e.g., in/out. of a. surface of device 100) or laterally (e.g,, back and forth in the same plane as a surface of device 100), In some embodiments, at least one tactile output genera tor sensor is located on the back of device 100, opposite touch screen display .112, which is located on the front of device 100.
(00691 Device 100 optionally also includes one or more accelerometers 168, FIG, 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 is, optionally, coupled to an input controller 160 in I O subsystem 106. Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Accelerationbased Theft Detection System lor Portable Electronic Devices,/’ and U.S. Patent Publication No. 200600.17692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety, in some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 1ÖÖ optionally includes, in addition to accelerometer(s) 168, a magnetometer (not shown) anti a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g,, portrait or landscape) of device 100.
(0070( In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, eontaet/motion module (or set of instructions) 130, graphics module (or set of instructions) 132. text inputmodule (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some
DK 2016 70622 A1 embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device/global internal state 157, as shown hi FIGS. 1A and 3. Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including Information obtained from the device’s various sensors and input control devices 116; and location information concerning the device's location and/or attitude.
(99711 Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,
WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
(0072( Communication module 128 facilitates communication with other devices over one or more external ports 124 and also ineludes various software components for handling data received by RF circuitry 108 and/or external port 124, External port 124 (e.g.. Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g,, the Internet, wireless LAN, etc,). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on IPod® (trademark of Apple Inc.) devices.
(9973( Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g,, detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touchsensitive surface (e.g., detecting one or more finger-dragging events), and determining if foe contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of
DK 2016 70622 A1 the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts t e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “muhitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 anddisplay controller 156 detect contact on a touchpad.
[0074( In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in. accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen dispiay can he set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click ‘ ‘intensity'” parameter).
(0075( Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event, followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as tire finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed bv detecting a finger-up (SiftolT} event.
(0076( Graphics module 132 includes various known software components tor rendering and displaying graphics on touch screen 112 or other display, including components tor changing the
4^4^
DK 2016 70622 A1 visual impact (e.g,, brightness, transparency, saturation, contrast, or oilier visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can. be displayed to a user, including, without limitation, text, web pages, icons (such as user-interlace objects including soft keys), digital images, videos, animations, and the like.
[0077] In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to he displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
|0078j Haptic feedback module 133 includes various software components for generating instructions used hy tactile output generators) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
JO079j Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in. various applications (e.g., contacts 137, e-mail 140, 1M 141, browser 147, and any other application that needs text input).
[ΘΘ8Θ] GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
|0O81j Applications 136 optionally include the following modules (or sets of instructions'!, or a subset or superset thereof;
* Contacts module 137 {sometimes called an. address book or contact, list);
* Telephone module 138;
* Video conference module 139;
* E-mail client module 140;
A*< ·.
DK 2016 70622 A1 • Instant messaging (IM) module 141;
• Workout support module 142;
• Camera module 143 for still and/or video unages, • Image management module 144;
» Video player module;
» Music player module;
» Browser module 147;
• Calendar module 148;
» Widget modules 149, which optionally include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
« Widget creator module 150 for making user-created widgets 149-6;
• Search module 151;
• Video and music player module 152, which merges video player module and music player module;
• Notes module I .
• Map module 154; and/or • Online video module 155, |0082j Examples of other applications 136 that are. optionally, stored m memory 102 include other word processing Applications, other image editing applications, drawing applications.
DK 2016 70622 A1 presentation applications, JAVA-enabted applications, encryption, digital rights management, voice recognition, and. voice replication, (0083] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application, internal state .192 of contacts module 137 in memory 102 or memory 370), including; adding name(s) to the address book; deleting name(s) from, the address book; associating telephone number(s), e-mail address(es), physical, address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate· communications by telephone· 138, video conference module 139, e-mail .140, or IM 141; and so forth.
(0084( In conjunction with KF circuitry 108, audio circuitry 110, speaker ill, microphone 113,touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module .138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module .137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
(0085( In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
(0086( In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module .130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client nx
DK 2016 70622 A1 module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143, (0087] hi conjunction with RF circuitry 108, touch screen I12, display controller 156, contact/raotion module 130. graphics module 132, and text input module 134. the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modi fy previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionaiiy include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
(0088] In conjunction with RF circuitry 108, touch screen I 12, display controller 156, contact-motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
(0089] in conjunction with touch screen 112, display controller 156, optical sensofis) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
(0000( In conjunction with touch screen 112, display controller 156, contact-motion module 130, graphics module 132, test input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify' (e.g., edit), or otherwise
DK 2016 70622 A1 manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images, (0091] hi conjunction with RF circuitry 108, touch screen 112, display controller 156, eontaet/motion module .130, graphics module 132, and text input module 134, browser module 1.47 includes executable instructions to browse the internet in. accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof as well as attachments and other files linked to web pages.
(0092} In conjunction with RF circuitry 108, touch screen 112, display controller 156, eontaettmotion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, todo lists, etc.) in. accordance with, user instructions, (0093( In conjunction with RF circuitry 108, touch screen 112, display controller 156, contactt/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created w idget 1496). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file, in some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g,, Yahoo
Widgets).
(0094( In conjunction with RF circuitry 108. touch screen 112. display controller L*to con tact.·'motion module 130, graphics module 132, text input module 154, and browser modute 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget), (0095( In. conjunction with touch screen 112, display controller 156, coniacl/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable Instructions to search for text, music, sound, image, video, and/or other files in memory 102 that
DK 2016 70622 A1 match one or nrøre search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
[0096] In conjunction with touch screen 112, display controller .156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry IOS, and browser module 147, video and music player module 1.52 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen I12 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
[00.97] In conjunction with touch screen 11.2,. display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
|0098| In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g,, driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions, (0099( In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker I I I , RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on. an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. in some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Additional descript ion of the online video application can be found in U.S. Provisional Patent
DK 2016 70622 A1
Application No, 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed June 20, 2007, and U.S. Patent Application No. 11,968,067, “Portable Multifunction Device, Method, and Graphical User interface for Playing Online Videos,” filed December 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
jöl 00) Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g,, the computer-implemented methods and other information processing methods described herein). These modules {e.g,, sets o f instructions) need not he implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module .into a single module (e.g., video and music player module 152, FIG. 1 A), In some embodiments, memory
102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
(01011 in some embodiments, device 1ÖÖ is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. Byusing a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, di als, and the like) on device 1ÖÖ is, optionally, reduced.
(01021 The predefined set of functions that are performed exclusi vely through a touch semen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad, (01O3| FIG ί B is a block diagram illustrating exemplary components tor event handling tn accordance with some embodiments, in some embodiments, memory 102 (FIG. 1 A} or 370
DK 2016 70622 A1 (FIG. 3) includes event sorter 170 {e.g., in operating system 126) and a .respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390), [0104] Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. in some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/gSohal internal state 157 is used by event sorter 170 to determine which application(s) Is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
[0105] In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed, or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user, [0106} Event monitor 171 receives event information from petiphetais interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture}. Peripherals interlace 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, aecelerometer(s) 168, and/or microphone 113 (through audio circuitry 110), information that peripherals interlace 118 recei ves from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface, [0107j in some embodiments, event monitor 171 sends requests to the peripherals Interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event Information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
DK 2016 70622 A1 {Θ1Θ8 j in some embodiments, event sorter i 70 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
(010.9] Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
(0:110] Another aspect of the user interface associated with an application is a set of views, sometimes herein, called application views or user interfece windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in. which a touch is detected, is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
[0111 I Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event in most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
[0112 j Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events, hi some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that ail actively involved views should receive a particular sequence of sub-events. In oilier embodiments, even if touch
DK 2016 70622 A1 sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
[0113] Event dispatcher module 174 dispatches the event information to an event recognizer {e.g., event recognizer 180). in embodiments including active event recognizer determination module .173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173, In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
[0114] In some embodiments, operating system 126 includes event sorter 17Ö. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
[0115] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application’s user interlace. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers .180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user Interface kit (not shown) or a higher level object from which application 136-1 Inherits methods and other properties. In some embodiments, a respective event handler .190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater .178 to update the application internal state 192. Alternatively, one or more of the application views .191 Include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191, (0116] A respective event recognizer 180 receives event information (e.g., event data J 79) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184, In some embodiments, event recognizer
DK 2016 70622 A1
180 also includes ai least a subset of; metadata 183. and event delivery instructions 188 (which optionally include sub-event delivery instructions).
[0117] Event, receiver 182 receives event information. from event sorter 170. The event information includes information about a sub-event, tor example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction ofthe sub-event. In some embodiments, events include rotation ofthe device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current, orientation (also called device attitude) of the device, |0118] Event comparator 184 compares the event information to predefined event or subevent definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an e vent or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g,, predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others.
In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on. the displayed object for a predetermined phase, and a second l iftoff (touch end) for a predetermined phase, in another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on foe displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end).
In some embodiments, the event also includes information for one or more associated event handlers 190.
(0119j In some embodiments, event definition 187 includes a definition of*an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an.
DK 2016 70622 A1 application view in. which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit lest to determine which of the three user-interface objects is associated with the touch (subevent), if each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the subevent and the object triggering the hit test, [91 29| In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer’s event type, [9121) When a respective event recognizer 180 determines that the series of sub-events do not match am of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent subevents of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
(0122) In some embodiments, a respective event recognizer ISO includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event deli very system should perform sub-event delivery to actively involved event recognizers, in some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether subevents are delivered to varying levels in the view or programmatic hierarchy, [0123) In some embodiments, a respective event recognizer ISO activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190, Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view, in some embodiments, event recognizer
DK 2016 70622 A1
180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
[G.124] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler, instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively invoived views receive the event information and perform a predetermined process.
|G125J in some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1, For example, object updater 17 7 creates a new user-interface object or updates foe position of a user-interface object GUI updater 178 updates the GUI, For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
|0ί 2f>l in some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 17S. In some embodiments, data updater i~6, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
I'O'l 27J it shall he understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to oilier forms of user inputs to operate multifunction devices 100 with input devices, not uh of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated witli single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
DK 2016 70622 A1 {0128j HG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (Ul) 200, In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100, In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not. select the corresponding application when the gesture corresponding to selection is a tap.
|0129{ Device 100 optionally also include one or more physical buttons, such as “home or menu button 204, As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100, Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
{0130J In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124, Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113, Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting in tensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
DK 2016 70622 A1 {0131 j FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child’s learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes inpuvoutput (I/O) interface 330 comprising display 340, which is typically a touch screen display, I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. I A), sensors 359 (e.g., optical, acceleration, proximity, touchsensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. I A). Memory 370 includes 'high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310, In some embodiments, memory 370 stores programs, modules, and data structures anal ogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 1.00 (FIG, 1A), or a subset thereof Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in .memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation moduie 382, word processing moduie 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable muitiinnction device 100 (FIG. 1 A) optionally does not store these modules.
{0132 j Each of the above-identified elements in FIG. 3 is. optionally, stored in one or more of the previously mentioned memory devices. Each, of the above-identified .modules corresponds to a set of instructions for performing a function described above. The above-identified modules
DK 2016 70622 A1 or programs (e.g, sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments, to some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.
|0133| Attention ts now directed towards embodiments ol’ user interlaces that are, optionally, implemented on, tor example, portable multi function device 100.
10134 } FIG . 4A ill ustrates an exemplary user interface tor a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof;
• Signal strength indicators) 402 for wireless communication(s), such as cellular and WiFi signals;
« Time 404;
• Bluetooth indicator 405;
« Battery status indicator 406;
* Tray 408 with icons for frequently used applications, such as:
c Icon 416 for telephone module 138, labeled “Phone. which optionally includes an indicator 4 J 4 of the number of missed calls or voicemail messages;
o Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails;
o icon 420 for browser module 147, labeled “Browser;” and o Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc·,} module 152, labeled “iPod;” and * Icons for other applications, such as;
DK 2016 70622 A1 o kon 424 for IM module 141, labeled “Messages;” o icon 426 for calendar module 148, labeled “Calendar;” icon 428 for image management module 144, labeled “Photos;” ø Icon 430 for camera module 143, labeled “Camera;” ø Icon 432 for online video module 155, labeled ‘Online Video;” ο Icon 434 for stocks widget 149-2, labeled “Stocks;” ø Icon 436 for map module .154, labeled “Maps;” ο Icon 438 for weather widget 149-1, labeled “Weather;” ο Icon 440 for alarm clock widget 149-4, labeled “Clock;” ο icon 442 for workout support module 142, labeled “Workout Support;” o icon 444 for notes module 153, labeled “Notes;” and o Icon 446 for a settings application or module, labeled “Settings,” which provides access to settings for device .100 and its various applications 136.
(0135] It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled “Music” or “Music Player.” Other labels are, optionally, used lor various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.
(0136] FIG. 4B illustrates an exemplary user interface on a device (e.g,, device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG, 3} that is separate front the display 450 (e.g., touch screen display i 12). Device 300 also, optionally, includes one or more contact intensity·' sensors (e.g„ one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.
(0137] Although some of the examples that follow wil l be given with reference to inputs on touch screen display·' 112 (where the touch-sensitive surface and the display' are combined), in
DK 2016 70622 A1 some embodiments, the device detects inputs on a touch-sensitive surface that is separate -from the display, as shown in FIG. 4B. in some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g,, 452 in FIG, 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g,, 450). In accordance with these embodiments, the device detects contacts (e.g,, 460 and 462 in FIG, 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG, 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4.B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein, |0138| Additionally, while tire following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, m some embodimenis, one or more of the finger inputs are replaced with input from another input device (e.g,, a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g,, instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact).
As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously, |0139j FIG. 5A illustrates exemplary personal electronic device 500, Device 500 includes body 502. In some embodiments, device 500 can include some or ail of the features described with respect to devices 100 and 300 (e.g., FIGS. IA-4B). In some embodiments, device 500 has touch-sensitive display screen 504» hereafter touch screen 504, Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the tonch-sensitive surface)
DK 2016 70622 A1 can provide output data toat represents toe intensity of touches. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.
[0140( Exempl ary techniques for detecting and processing touch intensity are found, for example, in related applications: international Patent Application Serial No.
PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User interface Objects Corresponding to an Application;’ tiled May 8, 2013, published as W1PÖ Publication No. W0/2Ö13/169849, and International Patent Application Serial No.
PGT/US2013/069483, titled “Device, Method, and Graphical User interface for Transitioning Between Touch Input to Display Output Relationships,” filed November 11, 2013, published as WIPO Publication No. WO/2Ö14/.105276, each of which is hereby incorporated by reference in their entirety.
[0141( In some embodiments, device 500 has one or more input mechanisms 506 and 508. input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms, in some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
[0142( FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. I A, IB, and 3. Device 500 has bus 5.12 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518, I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, intensiiy sensor 524 {e.g., contact intensity sensor). In addition, I O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanist» 506 is, optionally, a rotatable
DK 2016 70622 A1 input device or a depressible and rotatable input device, for example, biput mechanism 508 is, optionally, a button, in some examples.
(0143] Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof all of which can be operatively connected to I/O section 514, (0144] Memoty’ 518 of personal electronic device 500 can include one or more nontransitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 800 anti 1000 (FIGS, 8 and IO). Personal electronic device 500 is not limited to the components and configuration of FIG . 5B, but can include other or additional components in multiple configurations.
(0145] As used here, the term affordance'' refers io a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 1ÖÖ, 300, and/or 500 (FIGS, 1, 3, and 5). For example, an image (e.g,, icon), a button, and text, (e.g,, hyperlink) each optionally constitute an affordance, (0146} As used herein, the term focus selector refers to an input element that indicates a current part of a user interface with which a user is interacting. Sn some imp lernen tat tons that include a cursor or other location marker, the cursor acts as a locus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g,, touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element fe.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input, hr some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4Ä) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a focus selector” so that when axr input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g,, a button, window, slider, or other user interface element).
DK 2016 70622 A1 the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g,, by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally foe user interface element (or contact on a touch screen display) that is controlled by foe user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g,, a. cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate tire respective button (as opposed to other user interface elements shown on a display of the device).
(9.147( As used in the specification and claims, foe term characteristic intensity of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05,0.1, 0.2, 0.5, 1,2,
5,10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or alter detecting a decrease in intensity of the contact), A characteristic· intensity of a contact is, optionally, based on one or more of; a maximum value of the intensities of foe contact, a mean value of the intensities of the contact, an average value of the intensities of tire contact, a fop 10 percentile value of the intensifies of the contact, a value at the half maximum of foe intensifies of foe contact, a value at the 90 percent maximum of the intensities of the contact, or foe like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user.
DK 2016 70622 A1
For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold, hi this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation, in some embodirnents, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation}, rather than being used to determine whether to perform a first operation or a second operation.
(0148( FIG. 5C illustrates detecting a plurality of contacts 552A-552E on touch-sensitive display screen 504 with a plurality of intensity sensors 524A-524D, FIG. 5C additionally includes intensity diagrams that show the current intensity measurements of the intensity sensors 524A-524D relative to units of intensity. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 units of intensity, and the intensity measurements of intensity sensors 524B and 524C are each 7 units of intensity. In some implementations, an aggregate intensity is the sum of the intensity measurements of the plurality of intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a portion of the aggregate intensity. FIG. SD illustrates assigning the aggregate intensity to contacts 552A-552E based on their distance from the center of force 554, In this example, each of contacts 552A, 552B, and 552E are assigned an intensity of contact of 8 intensity units of the aggregate intensity, and each of contacts 552C and 552D are assigned an intensity of contact of 4 intensity units of the aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensify Ij that is a portion of the aggregate intensity. A, in accordance with a predefined mathematical function, Ij ~ A (Dj/SDi), where Dj is the distance of the respective contact j to the center of force, and XDi is the sura of the distances of all the respective contacts (e.g., i~l to last) to the center of force. The operations described with reference to FIGS, 5Ü-5D can be performed using an electronic device similar or identical to device .100, 300, or 500. in some embodiments, a characteristic intensity of a contact is based on one or more intensifies of the contact, in some embodiments, the intensity sensors are used to determine a single characteristic intensity (e.g., a single characteristic intensity of a
DK 2016 70622 A1 single contact), It should be noted that the intensity diagrams are not part of a displayed user interface, but are included in FIGS. 5G-5D to aid the reader.
(0149( In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point tire intensity of the contact i ncreases. In this example, the characteristic intensity of the contact at the end loca tion is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm, In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
(öl SO'j The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which foe device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below' the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), foe device will move a focus selector tn accordance with movement of foe contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or foe deep press intensity threshold.
Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface fi gures.
DK 2016 70622 A1 (0151] An increase of characteristic intensity of the contact from an Intensify below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity teeshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact front an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity ofthe contact from an intensity below the contactdetection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touchsurface. A decrease of characteristic intensity of the contact from an intensity above the contactdetection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contac t from the touch-surface. In some embodiments, tlie contact-detection intensity threshold is zero, in some embodiments, the contact-detection intensity threshold is greater ten zero.
|O1521 in some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase .in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respecti ve operation is performed in response to detecting the increase in intensity of the respecti ve contact abo ve the press-input intensity threshold (e.g., a “down stroke” of the respecti ve press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” ofthe respective press (0153] FIGS. 5E-5H illustrate detection of a gesture that includes a press input that corresponds to an increase in intensity of a contact 562 from an intensity below a light press intensity threshold (e.g,, “FTl”) in FIG, SE, to an intensity above a deep press intensity threshold (e.g., “ITd”) in FIG. 5H, The gesture performed with contact 562 is detected on touch-sensitive
DK 2016 70622 A1 surface 560 while cursor 576 is displayed over application icon 572B corresponding to App 2, on a displayed user interface 570 that includes application icons 572A-572D displayed in predefined region 574, In some embodiments, ihe gesture is detected on touch-sensitive display 504, The intensity sensors detect the intensity of contacts on touch-sensitive surface 560. Tbe device determines that the intensity of contact 562 peaked above the deep press intensity threshold (e.g., “IT»”). Contact 562 is maintained on touch-sensitive surface 560. In response to the detection of the gesture, and in accordance with contact 562 having an intensity that goes above the deep press Intensity threshold (e.g., ^sTTn”) during the gesture, reduced-scale representations 578.A578C (e. g., thumbnails) of recently opened documents for .App 2 are displayed, as shown in FIGS, 5F-5H. In some embodiments, the intensity, which is compared to the one or more intensity thresholds, is the characteristic intensity of a contact· It should he noted that the intensity diagram, for contact 562 Is not part ofa displayed user interface, but Is included in FIGS, 5E-5H to aid the reader.
10154( In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in FIG. 5F. As the animation proceeds, representation 578A moves upward and representa tion 578B is displayed in proximity of application icon 572B, as shown in FIG,
5G, Then, representations 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed in proximity of application Icon 572B, as shown In FIG. 5H, Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses in accordance with an intensity of contact 562, as shown in FIGS. 5F5G, where the representations 578A-578C appear and move upwards as the Intensity of contact 562 increases toward the deep press intensity threshold (e.g., “ITo ). In some enibodiments, the intensity, on which the progress of the animation is based, Is the characteristic intensity of the contact. The operations described with reference to FIGS, 5E-5H can he performed using an electronic device similar or identical to device .100, 300, or 500.
(0155( In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input, intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the
DK 2016 70622 A1 hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and tite respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g,, an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contactor the decrease in intensity of the contact, depending on. the circumstances), føl 56( For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below die hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity foreshold. Additionally, in examples where an operation is described as being -performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, foe operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, foe press-input intensity threshold, [0157( FIG, 6 illustrates exemplary devices connected via one or more communication channels to participate in a transaction in accordance with some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g,, a particular user input, an NFC field) and optionally transmit payment information
DK 2016 70622 A1 (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured io he NFC-enabled.
(0158} The electronic devices (e.g., devices 100, 300, and 500) are optionally configured to store payment account information associated with each of one or more payment accounts. Payment account information includes, for example, one or more of; a person’s or company's name, a billing address, a login, a password, an account number, an expiration date, a security code, a telephone number, a bank associated with the payment account (e.g,, an issuing bank), and a card network identifier. In some examples, payment account information includes include an image, such as a pic ture of a payment card (e.g,, taken by the device and/or received at the device). In some examples, the electronic devices receive user input including at least some payment account information (e.g., receiving user-entered credit, debit, account, or gift card number and expiration date). In some examples, the electronic devices detect at least some payment account information from an image (e.g,, of a payment card captured by a camera sensor of the device). In some examples, the electronic devices receive at least some payment account information from another device (e.g,, another user device or a server). In some examples, the electronic device receives payment account information from a server associated with another service for which an account for a user or user device previously made a purchase or identified payment account data (e.g., an app for renting or selling audio and/or video hies).
(0159} In some embodiments, a payment account is added to an electronic device (e.g., device 100, 300, and 500), such that payment account information is securely stored on the electronic device, in some examples, after anser initiates such process, the electronic device transmits information for the payment account to a transaction-coordination server, which then communicates with a server operated by a payment network for foe account (e.g., a payment server) to ensure a validity of foe .information. The electronic device is optionally configured to receive a script from the server that allows the electronic device to program payment information for foe account onto the secure element.
(0160( In some embodiments, communication among electronic devices 100, 300, and 500 facilitates transactions (e.g., generally or specific transactions). For example, a first electronic device (e.g., 100) can serve as a provisioning or managing device, and can send notifications of
DK 2016 70622 A1 new or updated payment account data (e.g., information for a new account, updated information for an existing account, and/or an alert pertaining to an existing account) to a second electronic device (e.g,, 500). in another example, a first electronic device (e.g,, 100) can send data to a second election device, wherein the data reflects information about payment transactions .facilitated at the first electronic device. The information optionally includes one or more of; a payment amount, an account used, a time of purchase, and whether a default account was changed. The second device (e.g., 5ÖÖ) optionally uses such information to update a default payment account (e.g., based on a learning algorithm or explicit user input).
[0161] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other over any of a variety of networks. For example, the devices communicate using a Bluetooth connection 608 (e.g., which includes a traditional Bluetooth connection or a Bluetooth Low Energy connection) or using a WiFi network 606. Communications among user devices are. optionally, conditioned to reduce the possibility' of inappropriately sharing information across devices. For example, communications relating to payment information requires that the communicating devices he paired (e.g., be associated with each other via an explicit user interaction) or be associated with a same user account.
[0162] In some embodiments, an electronic device (e g.. J 00, .100. 500) is used to communicate with a point-of-sale (POS) payment terminal 600, which is optionally NFCenabled. The communication optionally occurs using a variety of communication channels and/or technologies, in some examples, electronic device (e.g., 100, 300, 500} communicates with payment terminal 600 using an NFC channel 610. In some examples, payment terminal 600 communicates with an electronic device (e.g., 100, 300, 500) using a peer-to-peer NFC mode. Electronic device {e.g., 100, 300, 500) is optionally configured transmit a signal to payment terminal 600 that includes payment information for a payment account (e.g., a default account or an account selected for the particular transaction).
10163j in some embodiments, generation of and/or transmission of the signal is controlled by a secure element in the electronic device (e.g., 100, 300, 500). The secure element optionally requires a particular user input prior to releasing payment information. For example, the secure element optionally requires detection that the electronic device is being worn, detection of a
DK 2016 70622 A1 button press, detection of entry of a passcode, detection of a touch, detection of one or more option selections (e.g., received while interacting with an application), detection of a fingerprint signature, detection ofa voice or voice command, and or detection ofa gesture or movement (e.g,., rotation or acceleration). Io some examples, if a communication channel (e.g., an NFC communication channel) with another device (e.g., payment terminal 600) is established within a defined time period from detection of the input, the secure element releases payment information to be transmitted to the other device (e.g,, payment tenninal 600), in some examples, the secure element is a hardware component that controls release of secure information. In some examples, the secure element Is a software component that controls release of secure i nformation.
(0164( In some embodiments, protocols related to transaction participation depend on. for example. devtee Opes For example, a condition tor eeneuumg aud or transmuting payment information can be different for a wearable device (e.g., device 500) and a phone (e.g., device 100). For example, a generation and/or transmission condition for a wearable device includes detecting that a button has been pressed (e.g,, after a security verification), while a corresponding condition for a phone does not require fa niton-depression and instead requires detection of particular interaction with an application, tn some examples, a condition for transmitting and/or releasing payment information includes receiving particular input on each of multiple devices. For example, release of payment information optionally requires detection of a fingerprint and/or passcode at the device (e.g., device 100) and detection ofa mechanical input (e.g., button press) on another device (e.g., device 500).
(0165] Payment terminal 6ÖÖ optionally uses foe payment information to generate a signal to transmit to a payment server 604 to determine whether the payment is authorized. Payment server 604 optionally includes any device or system configured to receive payment information associated with a payment account and to determine whether a proposed purchase is authorized. In some examples, payment server 604 includes a server of an issuing bank. Payment tenninal 600 communicates with payment server 604 directly or indirectly via one or more other devices or systems (e.g., a server of an acquiring bank and/or a server of a card network).
(0166] Payment server 604 optionally uses at least some of foe payment information to identify a user account from among a database of user accounts (e.g., 602), For example, each
DK 2016 70622 A1 user account includes payment information. An account is, optionally, located by locating an account with particular payment information matching that from the POS communication. In some examples, a payment is denied when provided payment information is not consistent (e.g,, an expiration date does not correspond to a credit, debit or gill card number) or when no account includes payment information matching that from the POS communication.
[0I67[ in some embodiments., data for the user account further identities one or more restrictions (e.g,, credit limits); current or previous balances; previous transaction dates, locations and/or amounts; account status (e.g., active or frozen), and/or authorization instructions. In some examples, the payment server (e.g., 604) uses such data to determine whether to authorize a payment. For example, a payment server denies a payment when a purchase amount added to a current balance would result in exceeding an account limit, when an account is frozen, when a previous transaction amount exceeds a threshold, or when a previous transaction count or frequency exceeds a threshold.
(0168j In some embodiments, payment server 604 responds to POS payment terminal 600 with an indication as to whether a proposed purchase is authorized or denied. In some examples, POS payment terminal 600 transmits a signal to the electronic device (e.g., 100, 300, 500) to identify the result. For example, POS payment terminal 600 sends a receipt, to the electronic device (e.g,, 100, 300, 500) when a purchase is authorized (e.g., via a transaction-coordination server that manages a transaction app on the user device). In some instances, POS payment terminal 600 presents an output (e.g., a visual or audio output) indicative ofthe result. Payment can be sent to a merchant as part of the authorization process or can be subsequently sent.
[0169j In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that is completed without involvement of POS payment terminal 600, For example, upon detecting that a mechanical input has been received, a secure element in the electronic device (e.g., 100, 300, 500) releases payment information to allow an application on the electronic device to access the information (e.g., and to transmit the information to a server associated with die application), [0170] in some embodiments, the electronic dewce fe g , 100. 300. 5001 is m a locked state or an unlocked state. In the Socked state, the electronic device is powered on and operational but
NA
DK 2016 70622 A1 is prevented from performing a predefined set of operations in response to the user input. The predefined set of operations may include navigation between user interfaces, activation or deactivation of a predefined set of Junctions, and activation or deactivation of certain applications. The locked state may he used to prevent trn intentional or unauthorized use of some functionality of the electronic device or activation or deactivation of some functions on fhe electronic device. In the unlocked state, the electronic device 100 is power on and operational and is not prevented from performing at least a portion of the predefined set of operations that cannot he perfonned while in the locked state.
[0171) When the device is in the locked state, the device is said to be locked, in some embodiments, tire device in the locked state may respond to a limited set of user inputs, including input that corresponds to an attempt to transition the device to the unlocked state or input that corresponds to powering the device off, (0172) In some examples, a secure element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or an algorithm. In some examples, the secure element provides (or releases) payment information (e.g., an account number and/or a transaction-specific dynamic security code), fa some examples, the secure element provides (or releases) the payment information in response to the device receiving authorization, such as a user authentication (e.g., fingerprint authentication; passcode authentication; defecting doublepress of a hardware button when the device is in an unlocked state, and optionally, while fhe device has been continuously on a user’s wrist since the device was unlocked by providing autlrentieation credentials to the device, where the continuous presence of the device on the user’s wrist is determined by periodically checking that the device is in contact with the user’s skin). For example, the device detects a fingerprint at a fingerprint sensor (e.g., a fingerprint sensor integrated into a button) of the device. The device determines whether the fingerprint is consistent with a registered fingerprint. In accordance with a determination tliat the fingerprint is consistent with the registered fingerprint, the secure element provides (or releases) payment information. In accordance with a determination that the fingerprint is not consistent with the registered fingerprint, the secure element forgoes providing (or releasing) payment information.
DK 2016 70622 A1 f 0.173] Attention is now directed towards embodiments of user interfaces (“UF’) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 3()(), or device 500.
[0174] FIGS. 7A-7O illustrate exemplary user interfaces for transactions, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including tire processes in FIG. 8.
[0175] In some embodiments, electronic device 500A includes a display, one or more input devices, and. a hardware button (e.g., a mechanical button that is configured to enable a secure payment module to provide payment information for use in a payment transaction). In some embodiments, electronic device 500A is a smartwatch electronic device. In some embodiments, device 500A includes some or all of the features of device 100, device 300, or device 500.
[0176] As illustrated in FIG. 7A, the electronic device 500A displays, on the display', an application user interface 702 for a respective application (e.g., a third-party application), wherein the application user interface (e.g,, 702) includes a transaction aifordance (e.g., 70.2A) for requesting payment for activity associated with the respective application. In some examples, the electronic device displays a system user interface element (e.g., a time indicator 704A, a date indicator). In the example of FIG . 7A, the system user interface element 704A indicates the current time of day. In some examples, the system user interfece element indicates a day of the month, a currently logged in user account, name, a current location of the device, and/or an indication of the battery level for the electronic device 500A. In some examples, the electronic device 500A displays an indication 702B of the name of the respective application.
[0177j At FIG. 7B. while displaying the application user interlace fe g.. 702). the electronic device 500Λ defects, »a the one or more input debtees, selection of the transaction affordance 702A. in some examples, detecting selection of the transaction affordance 702A includes detecting a tap input at a location on a touch-sensitive surface of the electronic device 500A that eorresponds to the transaction affordance 702 A, [0178[ in some embodiments, as illustrated in FIGS. 7A-7B. the transaction affordance (e.g.. 702A) displayed in the application user interfece (e.g., 702) for the respective application is
DK 2016 70622 A1 provided (e.g,, to the respective application fer use in the application user interface) by a payment application ofthe eiectronic device (e.g., 500A) that is different from the respective application (e.g,, the transaction affordance is a button with an appearance and/or location determined by the payment application, such as a payment button that says “pay with wallet”).
In some examples, the payment application is a first-party application provided by the manufacturer of the electronic device, in some examples, the payment appli cation is an electronic wallet application with access to information that is personal to a user of the electronic device and the respective application does not have access to the information, in some examples, the information is payment information (e.g., account number, payment account number) of a payment account (e.g., a credit account) of the electronic wallet application. In some examples, the electronic wallet application has access to information for a plurality of payment accounts associated with the user of the electronic device 500A.
[0179j In some embodiments, as illustrated in FIGS. 7A-7B, the transaction affordance (e.g.,
7Ö2A) which, when activated, triggers display ofthe transaction user interface (e.g., 706) (e.g., by the payment application), is provided by the respective application (e.g., the transaction affordance is a button with an appearance and location determined by the respective application, such as a ride sharing payment button that says “request ride”), {0180{ FIGS. 7C and 7D illustrate alternative user interfaces. As illustrated in FIGS, 7C and 7D, in response to detecting selection of the transaction affordance (e.g., 702A), the electronic device 5Ö0A displays a transaction user interface (e.g,, 706) (e.g., replacing display ofthe application user interface 702 with display ofthe transaction user interface 706) that includes concurrently displaying transaction details (e.g., a payment amount 706B, a recipient of the payment 706C, a name of the respective application, an amount of tax, an indication 706D that the cost of the activity is variable) for the activity associated with the respective application and instructions (e.g., 706A) to activate the hardware button ofthe device 500A to authorize payment for the activity associated with the respective application.
{0181 j In some embodiments, the respecti ve application is a third-party application. In some examples, prior to displaying the application user interface 702 for the respective application, the electronic device receives a user-provided request to download and install the respective
DK 2016 70622 A1 application, in some examples, prior to displaying foe application user interface 702 for the respective application, foe electronic device receives a user-provided request to download and install the respective application. In some examples, the electronic device is configured to allow the respective application to be uninstalled or deleted from the electronic device based on a user request.
jöi821 in some embodiments, the activity associated with the respective application includes one or more of: a request for transportation, a request for ride sharing, purchasing a service, purchasing a product, and conducting a peer-to-peer transaction. In some examples, the activity associated with the respective application is a request for transportation. In some examples, the activity associated with the respective application is a request lor ride sharing. In some examples, the activity associated with the respective application is purchasing a service, in some examples, foe activity associated with the respective application is purchasing a product. In some examples, the activity associated with the respective application is conducting a peer-topeer transaction.
|D183| In some embodiments, as illustrated m FIG. 7(7 if the activity has a variable cost, foe information about the cost of the activity indicates that the transaction has a variable cost (e.g,, 7Ö6D, a “Pending” indication at foe top of foe user interface 706, with a total charged amount displayed at a bottom of the UI when the Ui is scrolled). In some embodiments, in accordance with a determination that the activity has a variable cost, the transaction details include an indication (e.g., 706D) that the activity has a variable cost. For example, information 706D includes foe language “pending amount⁵’ to indicate that the cost of the activity will be determined after the activity concludes (e.g., after the user completes a ride in using the rideshare system). In some examples, in response to receiving input (e.g,, detecting a scroll gesture on the touch-sensitive surface, detecting rotation of a rotatable input mechanism) corresponding to an instruction to scroll foe transaction user interface 706, the electronic device scrolls the transaction user interface 706 on foe display to display a total cost lor payment.
|t)184j In some embodiments, as illustrated in FIG. 7D, foe transaction details include information (e.g,, 7Ö6B) about a cost of the activity. In some examples, the transaction details
DK 2016 70622 A1 include a total cost for the activity. In some examples, the transaction details include a shipping cost for the activity (e.g., cost to ship a product).
(0.185] hr some embodiments, as illustrated in FIGS, 7C-7E, displaying the transaction user interlace (e.g., 706) further includes (e.g,, concurrently) displaying a graphical representation (e.g,, 706E) of a payment account with which payment will be made (e.g,, by the electronic device 500A) if' authorization io proceed with the payment transaction is received (e.g., via a double press of the hardware button by the user). In some examples, the payment account is a default payment account. In some examples, the payment account is a payment account selected by the user for payment for the activity. In some examples, the graphical representation of the payment account includes a depict ion of a physical payment card (e.g., depiction of an American Express card) associated with the payment account. In some examples, in response to receiving input (e.g,, detecting a scroll gesture on the touch-sensitive surface, detecting rotation of a rotatable input mechanism) corresponding to an instruction to scroll the transaction user interface 706, the electronic device scrolls the transaction user interface 706 on. the display to display the graphical representation ofthe payment account. In some examples, an electronic wallet application of the electronic device stores the payment account (and, optionally, one or more additional payment accounts). The payment account (and, optionally, the one or more additional payment accounts) is an account of* the user ofthe electronic device.
jOISfjj In some embodiments, as illustrated in FIGS. 7C-7E, the instructions (e.g., 706A) to activate the hardware button are displayed at a location on the display. In some examples, as illustrated in FIGS. 7C-7.E, the location, on the display corresponds to (e.g., is adjacent to) the hardware button of the electronic device.
(0.187] In some embodiments, as illustrated in FIGS. 7F.-7F.while displaying the transaction user interface (e.g,, 706) that includes the transaction details (e.g., 7Ö8A, 7O8B, contact information, shipping address, tax, total cost) and the instructions (e.g., 706A) to activate the hardware button, receiving input, via the one or more input devices (e.g,, detecting a scroll gesture on the touch-sensiti ve surface, detecting rotation of a rotatable input mechanism), corresponding to an instruction (e.g., a user request to the electronic device 500A) to scroll the transaction user interface (e.g., 706). In some examples, in response to receiving, the input
DK 2016 70622 A1 corresponding to fee instruction to scroll the transaction user interlace (e.g., 706): the electronic device 5ÖÖA displays (e.g., by scrolling the transaction user interface (e.g,, 706) to reveal), on the display, additional transaction details (e.g,, billing address 708A, contact information 708B, shipping address, tax, total cost) for the activity associated with the respective application.
[0188] In some embodiments, the electronic device does not scroll the instructions (e.g., 706A) to activate the hardware button, even when the user performs the scroll gesture. In some examples, the instructions (e.g., 706A) to activate the hardware button are displayed at a location on the display that is determined based on a location of the hardware button. In some examples, the instructions (e.g., 706A) are displayed near the hardware button to inform the user that the button can he activated to authorize payment. In some embodiments, as illustrated in FIGS. 7C7.E. and 7K, in accordance with a determination that the hardware button is in a first location (e.g., due to an orientation of the device), the electronic device 5ÖÖA displays the instructions 706A at a first location on the display (e.g., above a representation of the payment amount 706B and adjacent to the hardware button on the device 500A), In some embodiments, as illustrated in FIG. 70, in accordance with a determination that the hardware button is in a second location, the electronic device 500.4 displays the instructions 706A at a second location on the display that is different from the first location (e.g., below a representation of the payment amount 706B and adjacent to the button on die device 500A), In some examples, displaying additional transaction details for the activity associated with the respective application includes; foregoing scrolling the instructions to activate the hardware button (e.g., maintaining display of the instructions (e.g,, 706A) to activate die hardware button, and scrolling the additional transaction details (e.g.,
708.4, 7O8B) onto the display (e.g., onto a location of the instructions to activate the hardware button), in some examples, the instructions to activate the hardware button remains displayed (at least initially) at the location on the display while die additional transaction details scrolls onto the display, in some examples, the instructions (e.g., 706) to activate the hardware button lades (without scrolling) out on the display while the additional transaction details scrolls onto the display, in some examples, electronic device 500A fades away the instructions (e.g,, 706) to activate the hardware button as the electronic device scrolls the transaction user interface (e.g., 706) to reveal the additional transaction details. As a result, the electronic device does not vary the location of the instructions to activate the hardware button because the location of the instruction to activate the hardware button is tied to the location of the physical hardware button.
DK 2016 70622 A1 {0189] in some embodiments, the additional transaction details (e.g., 708A, 708B) scroll on top of the instructions (e.g., 7Ö6A). hi some examples, the scrolling causes hie additional transaction details (e.g,, 7Ö8A, 7Ö8B) to at first partial ly cover the instructions (e.g,., 706A) and subsequently to fully cover the instructions (e.g,, 706A), in some embodiments, displaying additional transaction details for the activity associated with the respective application includes: scrolling the additional transaction details (e.g., 7Ö8A, 7Ö8B) onto the display such that the additional transaction details obscure (fully, partially, or replace) foe instructions to activate the hardware button. As a result, the electronic device 500A does not vary the location, of the instructions to activate the hardware button because the location of the instruction to activate the hardware button is tied to the location of the physical hardware button.
{0190j In some embodiments, as illustrated in FIGS. 7G-71, a tap gesture on an additional transactions detail (e.g., 7Ö8A or 708B) allows the user to select from among different options for the additional transaction detail. In. some embodiments, as illustrated in FIG. 7G, while displaying the additional transaction details (e.g., 7G8A, 708B), the electronic device 5ÖÖA detects, via the one or more input devices, selection of a first detail (e.g., 7Ö8B) of the additional transaction details (e.g,, 7Ö8.A, 7Ö8B). .As illustrated in FIG. 7H, in response to detecting selection, of (e.g., detecting activation of the affordance corresponding to) the first detail (e.g., 708B) of the additional transaction details, the electronic device 5ÖÖA displays one or more options (e.g., 7f0A, 71 OB, 7I0C) for the first detail.. In some examples, displaying the one or more options includes replacing display of the additional transaction details (e.g,, 708A, 708B,
IOC) with display of the one or more options (e.g., 71ÖA, 71ÖB, 710C).
|0191) In some embodiments, in accordance with the transaction user interface being displayed (e.g., as in FIGS. 7C-7L): the electronic device 500A monitors (e.g., at all times that the transaction user interface is displayed) the hardware button lor activation (e.g,, monitoring for a double-press of the hardware button). As illustmted in FIGS. 71 and 7K, the electronic device detects activation of the hardware button (e.g,, detecting a double-press of the hardware button ). In some examples, FIG, 71 and 7K are alternative flows of the technique, ill ustrating that the electronic device 500A is enabled to detect activation of the hardware button while different user interfaces (e.g., of the payment application) are displayed. In some examples, the activation of the hardware button is detected while the device is in an unlocked state (and.
DK 2016 70622 A1 optionally, while the device has continuously been on a user’s wrist since the device was unlocked by providing authentication credentials to the device, where the continuous presence of the device on the user’s wrist is determined by periodically checking that the device is in contact with the user’s skin). In some examples, as illustrated in FIG. 7M and 7N, in response to detecting activation of the hardware button, in accordance with a determination that the activation of the hardware button meets transaction authorization criteria (e.g., a double press input where the press inputs are received within a predetermined time threshold of each other and optionally that the contact on the button meets user authentication criteria such as matching a fingerprint in a fingerprint database or having been unlocked and maintained on a user’s waist since being unlocked, and, for example.. In accordance with a determination that there is no error with the transaction parameters), the electronic device 5ÖÖA proceeds with a transaction (e.g., proceeding with making payment, transmitting payment information) for the activity (e.g., using the payment account of an electronic wall et of tire electroni c device). In some examples, in response to detecting activation of the hardware button, in accordance with a determination that the activation of the hardware button does not meet the transaction authorization criteria, the electronic device 500A forgoes authorizing the transaction and, optionally, displays a different user interface that corresponds to the activation of the hardware button (e.g., displaying representations of a set of recently used apps or displaying representations of a plurality' of contacts of the user in response to a single press of the hardware button). For example, a double press of the hard ware bu tton results in proceeding with the transaction and a single press of the hardware button results in displaying a user interface for a different application. In some embodiments, the electronic device 500A detects activation (e.g. double press) of the hardware but ton and, in response, i f transaction details are OK, proceeds with tire transaction (as i llustrated in FIGS. 7M-7N), and, if transaction details are not OK, displays an error (as illustrated in FIGS. 7J and 71,).
101.92( In some embodiments, as illustrated in FIG. 71 and 7K, the electronic device 500A detects activation of the hardware button (e.g., detecting a double-press of the hardware button). As illustrated in FIGS. 7M-7N, in response to detecting activation of the hardware button, in accordance with a determination that transaction processing criteria have been met, including a criterion that there is no error with the transaction parameters (and, optionally, that tire activation of the hardware button meets transaction authorization criteria), the electronic device 500A
DK 2016 70622 A1 proceeds with a transaction (e.g., proceeding with making payment, transmitting payment information) for the activity (e.g,, using the payment account of an electronic wailei of the electronic device), fn some examples, the activation of the hardware button is detected while the device is in an unlocked state (and, optionally, while the device has continuously been on a user’s wrist since the device was unlocked by providing authentication credentials to the device, where the continuous presence of the device on the user’s wrist is determined by periodically checking that the device is in contact with the user’s skin). As illustrated in FIGS. 7J and 7L, in response to detecting acti vation of the .hardware button, in accordance with a determination that there is an error with the transaction parameters (e.g., and thus, that the transaction processing criteria, that require that there are no errors with the transaction parameters, have not been met), the electronic device 500A displays, on the display, an error notification (e.g., 708C, 712) indicating that an error has been detected instead of proceeding with the transaction (e.g., foregoing proceeding with the transaction for the activity ).
|0103] In some embodiments, in accordance with the determination that there is an error with the transaction parameters, the electronic device receives (e.g., front the user) user input, via the one or more input devices (e.g., audio via a personal assistant, detecting activation of an affordance corresponding to an alternative contact 710B), at the electronic device 500A, In response to receiving the user input at the electronic device 500A, the electronic device modifies (e.g., to correct) the transaction parameters based on the user input, in some examples, once the error with the transaction parameters has been corrected, the device will proceed with the transaction in response to detecting an input authorizing the transaction (e.g., activation of the hardware button that meets transaction authorization criteria). In some examples, the error with the transaction is resolved, using foe techniques described with reference to FIGS, 0Ä-0N and method 1000.
|0194j In some embodiments, in accordance with the determination that there is an error with the transaction parameters, the electronic device receives (e.g., from the user) a request to correct the error (e.g., selection of the error notification), in response to receiving the request to correct the error, in accordance with a determination that potentially compatible transaction parameters are available on the electronic device 5ÖÖA (e.g., in a phone contacts application or database), the electronic device 500A displays one or more of the potentially compatible transaction
DK 2016 70622 A1 parameters (e.g,, 71 OA, 71GB). In some examples, the potentially compatible transaction parameters (e.g., 7IGA, 71 OB) are displayed along with a selectable option (e.g., 7IOC) to enter additional transaction parameters on a companion device that is different from the electronic device (e.g., an option 7IOC which, when selected, initiates a process for entering additional transaction parameters on a companion device as described below with reference to FIGS. 9A9N and method 1000 of FIG, 10), in response to receiving the request to correct the error, in accordance with a determination that potentially compatible transaction parameters are not available on the electronic device, the electronic device 500A displays instructions to enter additional transaction parameters on a companion device (e.g., electronic device 300 of FIG, 9G) that is different from the electronic device 500Ä. (e.g., as described below with reference to FIGS. 9A-9N and method 1000 of FIG. 10).
{9195( In some embodiments, as illustrated in FIGS. 7K-7L, displaying, on the display, the error notification (e.g., 708C) indicating tliat an error has been detected ineludes replacing display of the instructions (e.g., 706A) to activate the hardware button with display of the error notification (e.g., 7Ö8C). In some examples, displaying the error notification includes changing display of the transaction details (e.g., changing a color of the payment amount for the payment transaction).
{0196( In some embodiments, the user can switch among payment accounts. In some embodiments, the electronic device 500A receives user input, via the one or more input devices (e.g., a swipe gesture on a touch-sensitive surface at a location corresponding to the graphical representation 706E of the payment account ), corresponding to an instruction to select a payment account from among a plurality of payment accounts of an electronic wallet of the electronic device 500A. In response to detecting the user input corresponding to the instruction to select the payment account from among a plurality of payment accounts, the electronic device 500A selects the payment account for use in the transaction for the activity (e.g., without leaving the transaction user interface). In some examples, switching a payment account ineludes switching between a plurality of payment accounts associated with different payment cards, and switching between the payment account includes selecting different representations of the payment cards.
In some examples, switching a payment account includes switching between a plurality' of payment accounts associated with a same payment card (e.g., a checking, savings, and credit
DK 2016 70622 A1 account associated with a same payment card), and displaying an affordanee for selecting an account associated with the payment card. In some examples, when switching from a payment account for a first payment card associated with a single account to a payment account for a second payment card associated with multiple accounts (e.g., in response to a leftward swipe on the representation of toe first payment card), the device display s an animation of an affordanee for selecting between the multiple accounts associated with the second payment card appearing, and when switching from the payment account associated with the first payment card to the payment account associated with the second payment card (e.g., in response to a rightward swipe on the representation of the second payment card), the device displays an animation of the affordanee for selecting between the multiple accounts associated with the second pay ment card disappearing, [9197( In some embodiments, display of an indication, such as an indication of payment, replaces display of a system user interface element. In some embodiments, displaying the transaction user interlace includes replacing a displayed system user interlace element (e.g,, a time indicator 7O4A, a date indicator) with an indication of payment (e.g., 704B). In some examples, the respecti ve application does not have the abil ity to replace the display of toe system user interface element (e.g., a time indicator 704A, a date indicator). Accordingly, by replacing the system user interface element (e.g., a time indicator 704A, a date indicator) when displaying toe transaction user interface, the electronic device informs toe user that the transaction is being handled by a trusted application (e.g., a first-party application, a system-level application, an operating system of the electronic device).
[0198( In some embodiments, as illustrated in FIG. 7M, proceeding with the transaction (e.g,, proceeding with making payment, transmitting payment information) for the activity (e.g., using the payment account of an electronic wallet of toe electronic device) includes; (e.g,, subsequent to detecting activation of the hardware button, and optionally, when toe electronic device is in an unlocked stale, and optionally, while the device is on a user’s wrist, such as by detecting that toe device is in contact with the user’s skin) requesting (e.g,, from the user) a passcode (e.g,, by displaying toe request 714 on toe display). In some examples, proceeding with the transaction (e.g., proceeding with making payment, transmitting payment information) for toe activity (e.g., using the payment account of an electronic wallet of the electronic device)
DK 2016 70622 A1 further includes detecting, via the one or more input devices, the passcode (e.g., as provided by the user). In. some examples, proceeding with the transaction (e.g., proceeding with making payment, transmitting payment infonnation) for the activity (e.g., using the payment account of an electronic wallet ofthe electronic device) includes transmitting (e.g,, to a remote server, to a payment processing service) tlie passcode (e.g., along with the payment information) for processing the transaction. Thus, in some examples, the user authenticates locally (e.g., at the electronic device) by activating (e.g,, via a double-press) the hardware button (e.g,, while the electronic device is unlocked) and the user authenticates to a remote server (e.g., a payment processing sendee) via the passcode. In some examples, the passcode is verified locally at the electronic device (rather than being transmitted for processing the transaction). If the passcode is consistent with an enrolled passcode, the electronic device transmits (e.g., via a wireless network connection) payment information to the remote server for the transaction, if the passcode is not consistent with an enrolled passcode, the electronic device forgoes transmitting the payment information to the remote server for the transaction and, optionally, alerts the user that the passcode was not consistent with the enrolled passcode. In some examples, the user is requested to provide one or more other forms of authentication after activating the hard ware button (e.g., biometric authentication with a fingerprint sensor on the device or on a companion device) prior to proceeding with the transaction.
(0199| In some embodiments, as illustrated in. FIG. 7N, the electronic device 500A displays an indication of proceeding with the transaction, an indication that pay ment has been provided, or an indication that the payment information has been transmitted. In some examples, the electronic device 500A displays, in response to proceeding with the transaction, a user interface including an amount (e.g,, 716A) ofthe transaction and an indication (e.g., checkmark 716B) that the transaction was successful.
(02-00] FIG. 8 is a flow diagram illustrating a method for managing transactions using an electronic device in accordance with some embodiments. Method 800 is performed at a device {e.g., 10Ö, 30t). 500, 500A) with a display, one or more input devices, and a hardware button. Some operations in method 800 are, optionally, combined, the order of some operations is, optionally, changed, and some operations are, optfonaily, omitted.
DK 2016 70622 A1 (020.1] As described below, method 800 provides an intuitive way for managing transactions. The method reduces the cognitive burden on. a user for managing transactions, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to participate in transactions more efficiently, such as by reducing the number of inputs the user is required to enter at the device, conserves power and increases the time between battery charges.
}6262| At block 802, the electronic device displays, on the display, an application user mterfhee (e g 02) for a respective application (e.g., a tlurd-party application), wherein the application user interface (e.g., 702) includes a transaction affordance (e.g., 7O2A) for requesting payment for activity associated with the respective application.
|0203j In accordance with some embodiments, the transaction affordance (e.g,, 702A) displayed in the application user interface (e.g,, 702) for the respective application is provided by a payment, application of the electronic device (e.g., 500A) that is different from the respective application, in some examples, the payment application is a first-party application provided by the manufacturer of the electronic device, in some examples, the payment application is an electronic wallet application with access to information that is personal to a user of the electronic device and the respective application does not have access to the information, in some examples, die information is payment information (e.g,, account number or payment account number) of a payment account (e.g., a credit account) of the electronic wallet application. In some examples, the electronic wallet application has access to information for a plurality of payment accounts associated with the user of the electronic de vice 500A.
(0204( In accordance with some embodiments, the transaction afloidance (e.g., 702A) that., when activated, triggers display of the transaction user interface (e.g,, 706), is provided by the respective application, in accordance with some embodiments, the respective application is a third-party application. In some examples, prior to displaying the application user interfece for a respecti ve application, the electronic device receives a user-provided request to download and install the respective application, in some examples, prior to displaying the application user interface for a respective application, the electronic device recei ves a user-provided request to download and install the respective application. In some examples, the electronic device is
DK 2016 70622 A1 configured to allow the respective application to be uninstalled or deleted from the electronic device based on a user request, in accordance with some embodiments, the activity associated with foe respective application includes one or more of a request for transportation, a request for ride sharing, purchasing a service, purchasing a product, and conducting a peer-to-peer transaction.
(0205( At block 804, while displaying the application user interface (e.g, device detects, via the one or more input devices, selection of the transaction . 702). foe electronic affordance. In some examples, detecting selection of the transaction affordance (e.g., 702A) includes detecting a tap input at a location on a touch-sensitive surface corresponding to the transaction af&rdauce {e.g., 7Ö2A).
(0206 j At block 806, in response to detecting selection of the transaction affordance (e.g.,
702A), the electronic device displays a transaction user interlace (e.g., 706} (e.g., replacing display of foe application user interface 702 with the transaction user interface 706} that includes concurrently displaying, at block 808, transaction details (e.g., a payment amount 706B, a recipient of the payment 706C, a name of the respective application, an amount of tax, an indication 06D that the cost of the activity is variable) lor the activity associated with the respective application, and, at block S10, instructions (e.g., 706Ä) to activate the hardware button of foe device to authorize payment for the activity associated with foe respective application. Thus, the electronic device, by providing a visual indication (via the instruction 706A) to foe user that foe state of the electronic device has changed to a state where the transaction (of which the transaction details 706B-706D are displayed) can be authorized via activation of the hardware button, indicates to foe user a change of state of foe device. In some examples, foe instructions (e.g., 706Ä) to activate the hardware button are displayed at a location on the display, in some examples, the location on the display corresponds to (e.g., is adjacent io) the hardware button of the electronic device.
(0207] In accordance with some embodiments, displaying the transaction user interface (e.g,, 706} further includes displaying a graphical representation (e.g,, 706E) of a payment account with which payment will be made if authorization to proceed with the payment transaction is received. In some examples, the payment account is a default payment account. In some
DK 2016 70622 A1 examples, the payment account Is a payment account selected hy the user lor payment for the activity. In some examples, the graphical representation of the payment account includes a depiction of a physical payment card associated with the payment account. In some examples, in response to receiving input corresponding to an instruction to scroll the transaction user interface (e.g., 706), the electronic device scrolls the transaction user .interface (e.g., 706) on tire display to display the graphical representation of the payment account, in some examples, an electronic wallet application of the electronic device stores the payment account (and, optionally, one or more additional payment accounts). The payment account (and, optionally, the one or .more additional payment accounts) is an account of the user of the electronic device.
|0208j In accordance with some embodiments, the transaction details include information t,e g , OoB) about a voM ol the actn jt. In some examples, the transaction details include a total cost for tire activity. In some examples, the transaction details include a shipping cost tor the activity. In accordance with some embodiments, in accordance with a determination that the activity has a variable cost, the transaction details include an indication te.g,, 7Ö6D) that the activity has a variable cost. Thus, the electronic device, by providin g a visual indication (via the indication 706D) that the detected transaction, has a variable cost, informs the user that the cost has not been finalized and that the user can perform a scroll operation (e.g., scroll down operation as illustrated in FIG. 7E) to see pre-charges or pre-authorization amounts (e.g,, “Total $8.00” as illustrated in FK3, 7F, even if those are not the final amounts), thereby improving the user-machine interface by reducing the risk of erroneous input. In some examples, in response to receiving input corresponding to an instruction to scroll the transaction user interface (e.g,, 706), the electronic device scrolls the transaction user interface (e.g., 706) on the display to display a total cost for payment. In some examples, in response to receiving input corresponding to an instruction to scroll the transaction user interface (e.g., 706), the electronic device scrolls the transaction user intertace (e.g., 706) on the display to display a pre-authorization amount (or a pre-charge amount), |0209j In accordance with some embodiments, while displaying the transaction user interface (e.g., 706) drat includes the transaction details (e.g,, 708A, 708B, contact information, shipping address, tax, total cost) and the instructions (e.g,, 706A) to activate the hardware button, the electronic device receives input, via the one or more input devices, corresponding to an
DK 2016 70622 A1 instruction (e.g... a user request to the electronic device 5ÖÖA) to scroll the transaction user interface (e.g., 706), and lu response to receiving the input corresponding to the instruction to scroll the transaction user interface (e.g., 706), the electronic device displays additional transaction details (e.g., 708A, 7O8B, contact information, shipping address, tax, total cost) for the activity associated with the respective application.
(0219) in accordance with sonic embodiments, the instructions (e.g.. 706A) to activate the hardware button are displayed at a location on the display that is determined based on a location of the hardware button (e.g., adjacent to the hardware button i. In some examples, in accordance with a determination that the hardware button is in a first location, displaying the instructions (e.g., 706A) at a first location on the display, and in accordance with a determination that the hardware button is in a second location, displaying the instructions {e.g., 7Ö6A) at a second location on ihe display that is different from the first location. Thus, by arranging the instructions (e.g., 706A) adjacent to the hardware button that should be activated to authorize the transaction, the user is informed of the proper hardware button (e.g,, from among multiple buttons) for authorizing the transaction and the user can avoid, extraneous (or erroneous) button presses, such as button presses of incorrect buttons that would cause the electronic device to transition to a state where activation of the hardware button (even the proper hardware button) does not authorize the transaction. In accordance with some embodiments, displaying additional transaction details for the activity associated with the respective application includes foregoing scrolling the instructions to activate the hardware button to activate the hardware button, and scrolling the additional transaction details (e.g.. 708.A, 708B) onto the display. In some examples, the instructions to activate the hardware button remains displayed at the location on the display while the additional transaction details scrolls onto the display. In some examples, the instructions (e.g., 706A) to activate the hardware button lades out on the display while the additional transaction details scrolls onto the display. By fading out, rather than scrolling, the instructions (e.g., 706A), the electronic device avoids misaligning tire instructions (e.g., 7Q6A) with a corresponding hardware button, thus user can avoid extraneous button presses, such as button presses of incorrect buttons that would cause the electronic device to transition to a state where activation of the hardware button (even the proper hardware button) does not au thorize the transaction. In some examples, electronic device lades away the instructions (e.g,, 706A) to activate the hardware button as the electronic device scrolls the transaction user interface (e.g..
DK 2016 70622 A1
706) to reveal the additional transaction details. As a result, the electronic· device does not vary the location ofthe displayed instructions (e.g-, 706A) to activate the hardware button because the location of the instruction to activate the hardware button is tied to the location of the physical hardware button. In accordance with some embodiments, displaying additional transaction details for the activity associated with the respecti ve application includes scrolling the additional transaction details (e.g., 7Ö8A, 708Ö) onto the display such that the additional transaction details obscure the instructions to activate the hardware button.
[02111 In accordance with some embodiments, while displaying the additional transaction details (e.g., 708A, 708B), the electronic device detects, via the one or more input devices, selection of a first detail (e.g., 7Ö8B) of the additional transaction details (e.g., 7Ö8A, 708B), and, in response to detecting selection of (e.g., detecting activation of the affordance corresponding to) the first detail (e.g., 708B) of the additional transaction details, the electronic device displays one or more options (e.g,, 710A, 71 OB, 710C) for the first detail. In some examples, displaying the one or more options includes replacing display of the additional transaction details (e.g., 7Ö8A, 708B) with display of the one or more options (e.g., 7I0A, 71ÖB, 710C), [0212 j In accordance with some embodiments, in accordance with the transaction user interlace being displayed, the electronic device monitors the hardware button for activation, detects activation ofthe hardware button, and, in response to detecting activation of the hardware button, in. accordance with a determination that the activation of the 'hardware button meets transaction authorization criteria, proceeds with a transaction for the activity, in some examples, in response to detecting activation ofthe hardware button, in accordance with a determination that the activation of the hardware button does not meet the transaction authorization criteria, the electronic device forgoes authorizing the transaction and, optionally, displays a different user interface that corresponds the activation ofthe hardware button.
[0213] In accordance with some embodiments, the electronic device detects activation ofthe hardware button, and. in response to detecting activation ofthe hardware button, in accordance with a determination that transaction processing criteria have been met, including a criterion that there is no error with the transaction parameters (and, optionally, that the activation ofthe hardware button meets transaction authorization criteria), proceeds with a transaction for the
DK 2016 70622 A1 activity, and, in accordance with a determination that there is an error with the transaction parameters, displays, on the display, an error notification (e.g., 708C) indicating that an error has been detected, instead of proceeding with the transaction. Thus, the electronic device provides a visual indication (e.g., 708C) of an automatically detected error condition (e.g., error with the transaction parameters), thereby prompting the user to provide input to correct the error. In some examples, the error with the transaction is resolved using the techniques described with reference to FIGS. 9A-9N and method 1000. In some examples, the activation of the hardware button is detected while the device is in an unlocked state (and, optionally, while the device .has continuously been on a user’s wrist since the device was unlocked by providing authentication credentials to the device, where the continuous presence of the device on the user’s wrist is determined by periodically checking that the device is in contact with the user’s skin).
[0214] In accordance with some embodiments, the electronic device, in accordance with the determination that there is an error with the transaction parameters, receives user input, via the one or more input devices (e.g., audio via a personal assistant, detecting activation of an affordance corresponding to an alternative contact 710B), at the electronic device, and, in response to receiving the user input at the electronic device, modifies tire transaction parameters based on the user input. Thus, the electronic device, by providing the user with the ability to provide input to correct the error condition (e.g,, foe error with the transaction parameters), reduces the need tor the user to perform compl icated na vigation of the user interface to correct the error condition, in some examples, once the error with the transaction parameters has been corrected, the electronic device proceeds with the transaction in response to detecting an input authorizing the transaction.
JÖ21S] In accordance with some embodiments, the electronic device, in accordance with the determination that there is an error with tire transaction parameters, receives a request to correct the error, and, in response to receiving the request to correct the error, in accordance with a determination that potentially compatible transaction parameters are available on. the electronicdevice, displays one or more of the potentially compatible transaction parameters (e.g., 710A,
71.0B), and, in accordance with a determination that potentially compatible transaction parameters are not available on the electronic device, displays instructions to enter additional transaction parameters on a. companion device that is different horn the electronic device. In
DK 2016 70622 A1 some examples, the potentially compatible transaction parameters (e.g., 710A, 7.1 OB) are displayed along with a selectable option (e.g., 710C) to enter additional transaction parameters on a companion device that is different from the electronic device (e.g,, an option 710C which, when selected, initiates a process for entering additional transaction parameters on a companion device). Thus, tire electronic device, by providing the user with a visual indication (e.g., 7O8C) of an automatically detected error condition (e.g., error with the transaction parameters, no ), prompts the user to provide input to correct the error.
(0216( In accordance with some embodiments, displaying, on the display, the error notification (e.g,, 708C) indicating that an error has been detected includes replacing display of the instructions (e.g., 706A) to activate the hardware button with display of the error notification (e.g., 708C). Thus, the electronic device, by providing the user with a visual indication (e.g., 708C) of an automatically detected error condition (e.g., error with the transaction parameters), prompts the user to provide input to correct the error and indicates to the user that in the current state, as a result of the error, the hardware button cannot be used to authorize the transaction. In some examples, the error with the transaction is resolved using the techniques described with reference to FIGS. 9A-9N and method 1000, In some examples, displaying the error notification (e.g., 7Ö8C) includes changing display of the transaction details (e.g., changing a color of the payment amount for the payment transaction).
(0217( In accordance with some embodiments, the elecUOnlc device receives user input, via the one or mom input devices (e.g., a swipe gesture, such as a left swipe gesture or a right swipe gesture, on a touch-sensiti ve surface at a location corresponding to the graphical representation 906E of the payment account), corresponding to an instruction to select a payment account from among a plurality of payment accounts of an electronic wallet of the electronic device, and, in response to detecting the user input corresponding to the instruction to select the payment account from among a plurality of payment accounts, selects the payment account for use in the transaction for the activity. In some examples, switching a payment account includes switching between a plurality of payment accounts associated with different payment cards, and switching between the payment account includes selecting different representations of the payment cards, in some examples, switching a payment account includes switching between a plurality of payment accounts associated with a same payment card (e.g., a checking, savings, and credit
DK 2016 70622 A1 account associated with a same payment card), and displaying an affordance for selecting an account associated with the payment card, in some examples, wären switching from a payment account for a first payment card associated with a single account to a payment account for a second payment card associated with multiple accounts, the device displays an animation of an affordance for selecting between the multiple accounts associated with the second payment card appearing, and when switching from the payment account associated with the first payment card to the payment account associated with the second payment card, the device displays an animation ofthe affordance for selecting between the multiple accounts associated with the second payment card disappearing, {0218) in accordance with some embodiments, displaying the transaction user interface includes replacing a displayed system user interlace element te g., a tune indicator 7Ö4.A, a date indicator) with an. Indication of payment (e.g,, 704B). Thus, by replacing the system user interface element (e.g., a time indicator 704A, a date indicator) when displaying the transaction user interface, the electronic device informs the user that the transaction is being handled by a trusted application (e.g., a first-party application, a system-level application, an operating system ofthe electronic device), and therefore the user avoids providing additional inputs to the electronic device to confirm that the transaction is being handled by a trusted application. In some examples, the respecti ve application does not have the ability to replace the dispiay of the system user interface element (e.g., a time indicator 704Ä, a date indicator).
{0219) In accordance with some embodiments, proceeding with the transaction for the activity includes, subsequent to detecting activation of the hardware button, and optionally, when the electronic device is in an unlocked state, and optionally, while the device is on a user’s wrist, such as hy detecting that the device is in contact with the user’s skin, requesting a passcode (e.g., by displayi ng the request 714 on the display), detecting, via the one or more input devices, the passcode, and transmitting (e.g,, to a remote server or to a payment processing service) the passcode (e.g., along with the payment information) for processing the transaction, hi some examples, the user authenticates locally (e.g., at the electronic device) by activating (e.g., via a double-press) the hardware button and the user authenticates to a remote server (e.g,, a payment processing sendee) via the passcode. In some examples, the passcode is verified locally at the electronic device, if the passcode is consistent with an enrolled passcode, the eiectronic device
DK 2016 70622 A1 transmits payment inlannation to the remote server for the transaction. If foe passcode is not consistent with an. enrolled passcode, the electronic device forgoes transmitting the payment information ίο foe remote server for foe transaction and, optionally, alerts the user that foe passcode was not consistent with the enrolled passcode, in some examples, foe user is requested to provide one or more other forms of authentication after activating the hardware button (e.g., biometric authentication with a fingerprint sensor) prior to proceeding with the transaction, [0220] Note that details of foe processes described above with respect to method 800 (e.g., FIG . 8) are also applicable in an analogous manner to the methods described below. For example, method 1.000 optionally includes one or more of foe characteristics of the various methods described above with reference to method 800. For example, transaction user interface 706 described with reference to FIGS. 7A-7O and FIG. 8 is, in some examples, analogous to the transaction user interlace 906 described with reference to FIGS. 9A-9N an FIG. 10. For brevity, these details are not repeated below.
(0221 ( FIGS. 9A-9N illustrate exemplary user interfaces for transactions, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 10.
(0222( In some embodiments, electronic device 500B includes a display, one or more input devices, and, optionally, a hardware button (e.g,, a mechanical button that is configured to enable a secure payment module to provide payment information for use in a payment transaction). In some embodiments, electronic device 50ÖB is a smartwatch electronic device. In some embodiments, device 500B includes some or all of the features of device 100, device 300, device 500, or device 500B.
(0223( lu some embodiments, as illustrated in FIG. 9A. the electronic device 500B displays a transaction user interface (e.g,, 906) that includes concurrently displaying: transaction details (e.g., a payment amount 906B, a recipient of the payment 9Ö6C, a name of the respective application, an amount of tax) for activity associated with a respective application and instructions (e.g., 906A) to activate foe hardware button of the device to authorize payment for a transaction for an activity associated with the respective application. In some examples, the electronic device 5ÖÖB also displays a graphical representation (e.g., 9Ö6E) of a payment account
DK 2016 70622 A1 with which payment will be made (e.g., by foe electronic device 500B) if authorization to proceed with the payment transaction is received (e.g., via a double press of the hardware button by the user).
(0224] As illustrated in FIG. 9 A, the electronic device 500B receives (e.g., from a user, based on a user input) a request (e.g., activation ofa hardware button and, optionally, a passcode or fingerprint authentication) to proceed with foe transaction using transaction parameters (e.g., phone number, email address, billing address, and/or shipping address), as described, for example, above with reference to FIGS. 7A-7O and method 800 of FIG. 8.
(0225] In some embodiments, as illustrated in FIG, 9B, in response to the request to proceed with the transaction, in accordance with a determination that transaction processing criteria have been met, including a criterion that there was no error with the transaction parameters, the electronic device 5ÖÖB proceeds (e.g., provided that there are no other impediments to proceeding with foe transaction) with the transaction. in some examples, proceeding with the transaction includes transmi tting payment information to a remote server or a payment processing server. In some embodiments, as illustrated in FIG. 9B, the electronic device 500B displays an indication of proceeding with the transaction, an indication that payment has been provided, or an indication that the payment information has been transmitted. In some examples, the electronic device 500B displays, in response to proceeding with foe transaction, a user interface including an amount (e.g., 906F) of tlie transaction and an indication (e.g., checkmark 906G) that the transaction was successful (0226] in some embodiments, proceeding with the transaction is further conditioned upon a determination as to whether or not the request to proceed with the transaction meets transaction authorization criteria (e.g,, a double press input where the press inputs are received within a predetermined time threshold of each other and optionally font the contact on the button meets user authentication criteria such as matching a fingerprint in a fingerprint database or having been unlocked and maintained on a user’s wrist since being unlocked), if foe request to proceed with the transaction does not meet the transaction authorization criteria, the device does not proceed (e.g., forgoes proceeding) with the transaction, and if request to proceed with the transaction meets the transaction authorization criteria, the device proceeds with the transaction.
DK 2016 70622 A1 [0227] As illustrated in FIG. 9C, in response to the request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters (e.g., and thus, that the transaction processing criteria, that require that there are no errors with the transaction parameters, have not been met), the electronic device displays an error notification (e.g., 908) indicating that an error has been detected. Thus, the electronic device 5008 informs the user of an error.
[0228] As illustrated in FIG. 9D, the electronic device 5008 receives, via the one or more input devices, a request to correct the error (e.g., detecting activation of the error notification 90S).
[0229] As illustrated in FIG. 9E, in response to receiving the request to correct the error, in accordance with a detemrination that potentially compatible transaction parameters are available on the electronic device (e.g., in a memory of the electronic device, in a contact, phone book of the electronic device), the electronic device 500B displays, on foe display, one or more of foe potentially compatible transaction parameters (e.g., 910A, 910B).
|0230[ in some embodiments, as illustrated in FIG. 9E, if there are potentially compatible transaction parameters, the electronic device selects a transaction parameter as a de&ult transaction parameter, in response to receiving foe request to correct the error, in accordance with the determination that potentially compatible transaction parameters are available on the electronic device (e.g., in a memory of the electronic device, in a contact phone book of the electronic device), the electronic device 500B updates foe transaction parameters to include a default transaction parameter of the potentially compatible transaction parameters for use in the transaction. In some examples, the electronic device displays an indication (such as a check mark) next to the selected delimit transaction parameter to indicate to foe user that the defeult transaction parameter is selected, in some examples, the electronic device displays, on the display, one or more affordances (e.g., 910A, 91ÖB) corresponding to one or more respective potentially compatible transaction parameters, in some examples, the user can activate one of the one or more affordances corresponding to one or more respective potentially compatible transaction parameters to cause the electronic device to update the transaction parameters. For
DK 2016 70622 A1 example, the electronic device receives activation of an affordance corresponding to a home address and updates the transaction parameters to include the home address for billing purposes.
[0231] As illustrated in FIG. 9F, in accordance with a determination that potentially compatible transaction parameters are not available on the electronic device 500B, the electronic device 500B displays, on the display, instructions (e.g., 912) to enter additional transaction parameters on a companion device (e.g., 300) that is different from the electronic device 500B. Thus, the electronic device, hy providing the user with a visual indication (e.g., 912) of an automatically detected error condition (e.g., potentially compatible transaction parameters are not available on the electronic device 500.B), prompts the user to provide input at a separate companion device to correct the error. In some examples, the companion device is a smart phone. In some examples, the companion device is a laptop device.
[0232] In some embodiments, the electronic device 500B transmits, to the companion device 300, a request regarding a transaction parameter entry user interface. As illustrated in FIG. 9G, in some examples, the companion device 300 displays an indication (e.g., 920,924) of the request regarding the transaction parameter entry user interface.
[0233] in some embodiments, activating the indication of the request regarding the transaction parameter entry user interface enables the user to quickly enter the transaction parameter. Thus, the electronic device, hy providing the user with a mechanism to enter the transaction parameter, reduces the number of user inputs required to access the mechanism. In some examples, as illustrated in FIG, 9G, activation (e.g,, by the user), on the companion device 300, ofthe indication (e.g., 924) ofthe request regarding the transaction parameter entry' user interface causes the companion device to display, on a display of the companion, device, the transaction parameter entry user interface (e.g,, 922). Thus, the electronic device, hy providing the user with a visual indication (e.g., 924) of an automatically detected, error condition (e.g., error with the transaction parameters, detected at the electronic device 500B), prompts the user to provide input to correct the error. In some examples, the transaction parameter entry user interlace is a user inter lace of a configuration application on the companion device that corresponds to the electronic device. In some examples, the configuration application is used hy the user on the companion device to configure the electronic device, in some examples, the
DK 2016 70622 A1 companion device .receives entry (e.g., using a virtual keyboard displayed on the display of fee companion device) of a transaction parameter, hi response to recei ving the transaction parameter, the companion device transmits the transaction parameter to the electronic device. Thus, the user can use the companion device, which in some examples is larger and has a more accommodating user interface for receiving user entry, for entering information (e.g,, an additional transaction parameter) that is needed (or helpful) at the electronic device 500B, [0234] In some embodiments, the user uses the transaction parameter entry user interlace (e.g., 922) of the companion device to enter information that is then sent the electronic device 5ÖÖB. in some examples, the electronic device 500B receives (e.g., from the companion device) a. respective additional transaction parameter. In some examples, the transaction parameter that the user enters (or selects, or otherwise provides) at the companion device is transmitted (e.g., hy the companion device) to the electronic device for use In the transaction.
[0235) In some embodiments, as illustrated in FIG. 91, in response to receiving the respective additional transaction parameter, the electronic device 500B updates the transaction user interface (e.g., 906) in accordance with the respective additional transaction parameter, on the display (e.g., based on the respective additional transaction parameter). Thus, the electronic device, by updating the transaction user interface (e.g,, 906), indicates to the user that the electronic device has received the update to the transaction parameters and, optionally, also indicates that the electronic device has transitioned to a state where activation of fhe hardware button authorizes the transaction. In some examples, in response to receiving the transaction parameter, the electronic device 500B updates the display. In some examples, in response to receiving the transaction parameter, the electronic device 500B updates the display to cease displaying the error notification (e.g., 908). in some examples, In response to receiving the transaction parameter, the electronic device 500B displays the transaction parameter, [0236) In some embodiments, in response to the instructions (e.g.. 912) in the transaction user interface on the electronic device 500B, the user causes the companion device 300 to open the companion application (e.g., 926) on the companion device 300 and the user is automatically presented with the transaction parameter entry user interface (e.g., 922). Thus, the electronic device, by providing the user with a visual indication (e.g,, 912) of an automatically detected
DK 2016 70622 A1 error condition (e.g., error with the transaction parameters, potentially compatible transaction parameters are not available on the electronic device 500Ö), prompts ihe user to provide input on the companion device (e.g., 300) to correct the error.
|0237j in some embodiments, the companion device 300 automatically launches the transaction parameter entry user interface (e.g., 922) on the companion device 300 in response to receiving the request regarding the transaction parameter entry user interface from the electronic device 500B. Thus, the companion device (e.g., 300), by providing the user with a visual indication (e.g,, transaction parameter entry user interface 922) of an automatical ly detected error condition (e.g,, error with the transaction parameters, potentially compatible transaction parameters are not available on the electronic device 500B), prompts the user to provide input to correct the error and without requiring the user to provide inputs to launch the transaction parameter entry user interface (e.g., 922).
|0238j In some embodiments, as illustrated in FIGS. 9J-9N, the companion device 300 displays an indication (e.g,, 920), which the user can activate to access a companion application on the companion device 300. Thus, the companion device, by providing the user with a visual indication (e.g., 708C) of an automatically detected error condition (e.g., error with the transaction parameters), prompts the user to provide input to correct the error and reduces the user inputs required to correct the error. For example, the companion application is configured to send information to the electronic device 500B.
|0239j As illustrated in FIG. 9.1, the companion device 300 receives (e.g., from a user) a request to open a companion application (e.g., 926). In some examples, receiving the request includes detecting activation of an afrordance (e.g., 920), such as an affordance displayed on a lock screen or an affordance displayed on a home screen of the companion device 300.
1Ö24Ö] As illustrated in FIG, 9K, the user activates an affordance (e.g., 920) on the companion device 300 that corresponds to the companion application. As illustrated in FIG. 9K, the companion device 300 displays the companion application 926, including various settings for the electronic device 500B. In some examples, the companion device 300 detects activation of an affordance 926A for accessing electronic wallet settings of the electronic device 500B. In response to detecting activation of the affordance 926.4 for accessing electronic wallet settings of
DK 2016 70622 A1 the electronic· device 500B, the companion device 300 displays one or room options 928A-928D, including an option (e.g., 928C) to access the transaction parameter entry oser interlace (e.g., 922) on the companion device 300, as illustrated in FIG. 9L. As illustrated in FIG. 9M, in response to detecting activation of the option (e.g., 928C) to access the transaction parameter entry user interface, the companion device 300 displays tire transaction parameter entry user interface (e.g., 922), in some examples, the transaction parameter entry user interface (e.g., 922) is used by the user on the companion device 300 to configure the electronic device, in some examples, the companion device 300 receives entry (e.g., rising a virtual keyboard displayed on the dispiay of the companion device) of a transaction parameter at the transaction parameter user interface, hi response to receiving the transaction parameter, the companion device 300 transmits the transaction parameter to the electronic device 500B, Thus, the user can use the companion device 300, which in some examples is larger and has a more accommodating user interface for receiving user entry, for entering information fe.g., an additional transaction parameter) that is needed (or helpful) at the electronic device 500B.
{0241} In some embodiments, in response to receiving the transaction parameter le g., from the companion device'), the electronic device 50013 updates the transaction parameters to include the respective additional transaction parameter for use in the transaction. Thus, for example, the technique reduces the number of inputs required on the electronic device to update the transaction parameters. For example, if the companion device transmits a mailing address to the electronic device, the electronic device will update the transaction parameters to use the respective additional transaction parameter. Thus, the respective additional transaction parameter is automatically selected for use in the transaction (e.g., the transaction during which the request regarding the transaction parameter entry user interlace was transmitted by the electronic device).
{0242j in some embodiments, in response to receiving the respective additional transaction parameter (e.g., from the companion device), fee electronic device 5008 displays, on the display, an indication of the respective additional transaction parameter. Thus, the electronic device, byproviding a visual indication (via indication of the respective additional transaction parameter) to the user that the electronic device has automatically detected the respective additional transaction parameter, indicates to the user that fee respective additional transaction parameter has been
DK 2016 70622 A1 received and, optionaiiy, that the electronic device has changed to a state where the transaction can be authorized via activation of the hardware button. While displaying the indication of the respective additional transaction parameter, the electronic device 500B detects activation of a hardware button of the electronic device (e.g., detecting a double-press of the hardware button), hi accordance with a determination that there is no error with the updated transaction parameters that include the respective additional transaction parameter, the electronic device 5ÖÖB proceeds with the transaction (e.g,, proceeding with making payment, transmitting payment information) for tbe activity (e.g,, using the payment account of an electronic wallet of the electronic device), in accordance with a determination that there is an error with the updated transaction parameters, the electronic device 500B displays, on the display, a second error notification indicating that an error has been detected, (and foregoing proceeding with the transaction for the activity). In some examples, if there is an error with the updated transaction parameters, the device repeats the process described above starting with FIG. 9A or 9C. In some examples, the activation of the hardware button causes the device to proceed with the transaction from any portion of the transaction user interface (e.g., even when the use has navigated through one or more menus to change a transaction parameter or enter a new transaction parameter for the transaction), so that the “click to pay” instruct ions do not need to be displayed in order for the device to proceed with the transaction in response to a request to proceed vvtth the transaction that meets transaction processing criteria. Thus, the electronic device, by not requiring the user to navigate the user interface to a particular display prior to authorizing the transaction using the hardware button, reduces the number of user inputs required to authorize the transaction.
(0243j In some embodiments, as illusteated io FIG. 9f, in response to receiving the respective additional transaction parameter (e.g,, from the companion device), the electronic device 500B displays, on the display, instructions (e.g., 906A) to activate a hardware button of the electronic device io authorize payment for the transaction. Thus, the electronic device, by providing a visual indication (via the instruction 906A) to the user that the electronic device has received the respective additional transaction parameter, indicates to the user r that the electronic device has received the respective additional transaction parameter and, optionally, that the electronic device has changed to a state where the transaction can be authorized via activation of the hardware button. In some examples, while displaying the instructions (e.g,, 906A) to activate a hardware button of the electronic device to authorize payment for the transaction, the electronic
DK 2016 70622 A1 device 500B forgoes displaying the respective additional transaction parameter, in some examples, the electronic device 500B detects activation of the hardware button (e.g., detecting a double-press of the hardware button). In response to detecting activation of the hardware button (e.g., when the electronic device is in an unlocked state, and optionally, while the device is on a user’s wrist, such as by detecting that the device is in contact with the user’s skin), in accordance with a determination that transaction processing criteria, have been met, including a criterion that there is no error with the updated transaction parameters, the electronic device 500B proceeds with a transaction (e.g,, proceeding with .making payment, transmitting payment information) for the activity (e.g., using the payment account of an electronic wallet of the electronic device). In some embodiments, in response to detecting activation of the hardware button (e.g., when the electronic· device is in an unlocked state, and optionally, while the device is on a user’s wrist, such as by detecting that the device is in contact with the user’s skin), in accordance with a determination that there is an error with the {ransaction parameters (e.g., and thus, that the transaction processing criteria, that require that there are no errors with the transaction parameters, have not been met), the electronic device 500B displays, on the display, an error notification (e.g,, 7ÖSÜ) indicating that an error has been detected (and foregoing proceeding with the transaction for the activity).
[0244( In some embodiments, in response to the request to proceed with the transaction. In accordance with the determination that there is an error with the transaction parameters, the electronic device 500B updates a displayed characteristic (e.g., location, size, color) of a displayed user interlace element (e.g., the price 906B) to indicate that the error has been detected. Thus, the electronic device, by providing the user with a visual indication (e.g., by updating the displayed characteristic) of an automatically detected error condition (e.g., error with the transaction parameters), prompts the user to provide input to correct the error. In some examples, toe price to be paid (e.g., 906B) changes color trom blue to red when the electronic device determines that toere Is an error with the transaction parameters. For example, this indicates to the user that there is an error with the transaction parameters.
[0245( In some embodiments, in response to receiving toe request to correct toe error, in accordance with the determination that potentially compatible transaction parameters are available on the electronic device (e.g., in a memory' of the electronic device, in a contact phone
DK 2016 70622 A1 book of foe electronic device), the electronic device 500B displays, on the display, an entry afibrdance (e.g., 9 IOC), which when activated, enables the user to provide a transaction parameter at the electronic device (e.g., via dictation, via user-selection from the contacts phone application, via the companion device, as discussed above with reference to FIGS. 9A-9F and method 1000 of FIG. 10), that is not included in the potentially compatible transaction parameters.
(0246] in some embodiments, the electronic dev tee 5OOB detects actis atton of the entry afibrdance (e.g., 9I0C). In response to detecting activation of entry affordance (e.g., 9IOC), the electronic device 500B monitors audio input received via a microphone of the electronic device 500B. The electronic device 5ÖÖB updates foe transaction parameters based on the audio input received via the microphone ofthe electronic device. For example, foe electronic device 50ÖB processes foe audio input to detect words and/or phrases and transcribing the words and/or phrases for use as a transaction parameter, or, optionally, interpreting the words and/or phrases as verbal instructions to retrieve stored data such as email addresses, phone numbers, physical addresses, for use as a transaction parameter.
(0247] In some embodiments, the electronic device 500B detects activation of the entry affordance (e.g., 9 IOC), In response to detecting activation of entry affordance (e.g,, 910C), the electronic device 500B displays one or more contacts (e.g., addresses, phone numbers) based on contacts (e.g., addresses, phone numbers ) stored in a contacts application. The electronic device 500B receives (e.g., from the user) selection of a contact of the one or more contacts. The electronic device 500B updates the transaction parameters based on the selected contact, |0248j In some embodiments, the electronic device 500B detects activation of the entry affordance (e.g., 9 IOC), In response to detecting activation of entry affordance, foe electronic device SÖGB transmits, to the companion device 300, a second request regarding a second transaction parameter entry user interface. In some examples, the companion device 300 displays a second indication of the request regarding the second transaction parameter entry user interface. In some examples, foe electronic device receives (e.g., from the companion device) a transaction parameter (e.g., in accordance with transmitting the second request). In some examples, the transaction parameter that the user enters (or selects, or otherwise provides) at foe
DK 2016 70622 A1 companion device is transmitted (e.g., by the companion device) to the electronic· device tor use in. the transaction. In some examples, in. response to receiving the transaction, the electronic device updates the transaction parameters based on the respective additional transaction parameter.
[0249] FIG. 10 is a flow diagram illustrating a method for managing transactions using an electronic device in accordance with some embodiments. Method 1000 is performed at a device (e.g., 100, 300, 500, 500B) with a display, one or mom input devices, and, optionally, a hardware button and microphone. Some operations in method IÖÖÖ are, optionaliy, combined, the order of some operations is, optionally, changed, and some operations are, optionally, omitted.
|0250j As described below, method 1000 provides an intuitive way for managing transactions. The method reduces the cognitive burden, on a. user for managing transactions, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to participate in transactions more efficiently, such as by reducing the number of inputs the user is required to enter at the device or allowing the user to provide inputs at a different device, conserves power and increases the time between battery charges.
(0251] At block 1002. the electronic de we recedes a request to proceed w ith a transaction using transaction parameters.
[0252j At block 1004, in response to the request to proceed with the transaction, in accordance vuth a determination that there is an error with the transaction parameters, the electronic device displays an error notification (e.g., 908) indicating that an error has been detected. In accordance with some embodiments, in response to the request to proceed with the transaction, in accordance with a determination that transaction processing criteria have been met, including a criterion that there was no error with the transaction parameters, the electronic device proceeds with the transaction. In some examples, proceeding with the transaction includes transmitting payment information to a remote server or a payment processing server, in some examples, proceeding with the transaction is further conditioned upon a determination as to whether or not the request to proceed with the transaction meets transaction authorization criteria; if the request to proceed with the transaction does not meet the transaction authorization criteria, the device does not proceed with the transaction, and if request fo proceed with the
DK 2016 70622 A1 transaction meets the transaction authorization criteria, the device proceeds wife fhe transaction, hi accordance with some embodiments, in response to the request to proceed with the transaction, in accordance with the determination that there is an error with the transaction parameters, the electronic device updates a displayed characteristic (e.g,, location, size, color) of a displayed user interface element (e.g., 906B) to indicate that the error has been detected, in some examples, the price to be paid te.g., 906B) changes color from blue to red when the electronic device determines that there is an error with the transaction parameters, thus indicating to the user that there is an error with the transaction parameters.
[0253( At block 1006, the electronic device receives, via the one or more input devices, a request to correct the error (e.g,, activation of the error notification 908), [0254( At block 1008, in response to receiving the request to correct the error, in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, at block 1010, the electronic device displays, on the display, one or more of the potentially compatible transaction parameters (e.g,, 910Ä, 9108), and, in accordance with a determination that potentially compatible transaction parameters are not available on the device, at block 1012, the electronic device displays, on the display, instructions (e.g,, 912) to enter additional transaction parameters on a companion device (e.g., 300) that is different from the electronic device.
[0255( In accordance with some embodiments, in response to receiving the request to correct the error, in accordance with the determination that potentially compatible transaction parameters are available on the electronic device, the electronic device updates the transaction parameters to include a default transaction parameter of foe potentially compatible transaction parameters for use in the transaction, and the electronic device displays, on the display, one or more affordances (e.g., 910A, 910B) corresponding to one or more respective potentially compatible transaction parameters. In some examples, the electronic device displays an indication (e.g., a check mark) next to the selected default transaction parameter to indicate to the user that the default transaction parameter is selected, in some examples, the user can acti vate one of the one or more affordances corresponding to one or more respective potentially compatible transaction parameters to cause the electronic device to update the transaction parameters. For example, the
DK 2016 70622 A1 electronic device receives activation of an affordance corresponding to a home address and updates the transaction parameters to include the home address for hilling purposes. In accordance with some embodiments, in response to receiving the request to correct the error, in accordance with the determination that potentially compatible transaction parameters are available on the electronic device, the electronic device displays, on the display, an entry affordance, which when activated, enables the user to provide a transaction parameter at the electronic device, that is not included in the potentially compatible transaction parameters.
|0256) In accordance with some embodiments, the electronic device detects activation of the entry affordance, in response to detecting activation of entry affordance, monitors audio input recei ved via a microphone of the electronic device, and updates the transaction parameters based on the audio input received via the microphone of the electronic device, in accordance with some embodiments, tire electronic device detects activation of the entry affordance, in response to detecting activation of entry affordance, displays one or more contacts (e.g., addresses, phone numbers) based on contacts (e.g., addresses, phone numbers) stored io a contacts application, receives selection of a contact of the one or more contacts, and updates the transaction parameters based on the selected contact. In accordance with some embodiments, the electronic device detects activation of the entry' affordance, and, in response to detecting activation of entry affordance, transmits, to the companion device, a second request regarding a second transaction parameter entry user interface, and the companion device displays a second indication of the request regarding the second transaction parameter entry user interface, hi some examples, the electronic device receives (e.g., from the companion device) a transaction parameter, in some examples, the transaction parameter that the user enters (or selects, or otherwise provides) at the companion device is transmitted (e.g., by the companion device) to the electronic device for use in the transaction. In some examples, in response to receiving the transaction, the electronic device updates the transaction parameters based on the respective additional transaction parameter.
[0257) In accordance with some embodiments, the electronic device transmits, io the companion device, a request regarding a transaction parameter entry user interface, and the companion device displays au indication (e.g,, 920) of the request regarding the transaction parameter entry user interface. In accordance with some embodiments, activation, on the
DK 2016 70622 A1 companion device, ofthe indication (e.g., 920) ofthe request regarding die transaction parameter entry user interface causes dispiay, on a display ofthe companion device, ofthe transaction parameter entry user interface (e.g,, 922). In some examples, the transaction parameter entry user interface is a user interface of a configuration application on the companion device that corresponds to the electronic device, in some examples, the configuration application is used by the user on the companion device to configure the electronic device, in some examples, the companion device receives entry (e.g., using a virtual keyboard displayed on the display of the companion device) of a transaction parameter. In response to receiving the transaction parameter, the companion device transmits the transaction parameter to the electronic device, fn accordance with some embodiments, in response to receiving the transaction parameter (e.g., from the companion device), the electronic device updates the transaction parameters to include the respective additional transaction parameter for use in the transaction, (0258] in accordance with some embodiments, the electronic device receives (e.g., from the companion device) a respective additional transaction parameter, and, in response to receiving the respective additional transaction parameter, updates a transaction user interface (e.g., 906) in accordance with the respective additional transaction parameter, on the display, in some examples, the transaction parameter that the user enters (or selects, or otherwise provides) at the companion device is transmitted (e.g., by the companion device) to the electronic device for use in the transaction, fn some examples, the companion device provides the respective additional transaction parameter when it is input on the companion device even if the companion device did not launch the transaction parameter entry» user interface based on information from the device, in some examples, in response io receiving the transaction parameter, the electronic device updates the display, fn some examples, in response to receiving the transaction parameter, the electronic device updates the display to cease displaying the error .notification (e.g., 90S). In some examples, in response to receiving the transaction parameter, the electronic device displays the transaction parameter.
|0259j In accordance with some embodiments, in response to receiving the respective additional transaction parameter (e.g.. from the companion device), the electronic device displays, on the display, an indication ofthe respective additional transaction parameter, and. while displaying the indication of the respective additional transaction parameter, the electronic
DK 2016 70622 A1 device detects activation of a hardware button of the electronic· device (e.g., detecting a doublepress of the hardware button), and, in accordance with a determination that there is no error with the updated transaction parameters that include the respective additional transaction parameter, the electronic device proceeds with the transaction tor the activity, and, in accordance with a determination that there is an error with the updated transaction parameters, the electronic device displays, on the display, a second error notification indicating that an error has been detected. In some examples, if there is an error with the updated transaction parameters, the device repeats the process described above starting with FIG. 9 A or 9C. In some examples, the activation of the hardware button causes the device to proceed with the transaction from any portion of the transaction user interlace.
[0260] In accordance with some embodiments, in response to receiving the respective additional transaction parameter (e.g., from the companion device), the electronic device displays, on the display, instructions (e.g., 906A) to activate a hardware button of the electronic device to authorize payment for the transaction, the electronic device detects activation of the hardware button (e.g., detecting a double-press of the hardware button), and, in response to detecting activation of the hardware button (e.g., when the electronic device is in an unlocked state, and optionally, while the device is on a user’s wrist, such as by detecting that the device is in contact with the user’s skin), in accordance with a determination that transaction processing criteria have been met, inchiding a criterion that there is no error with the updated transaction parameters, the electronic device proceeds with a transaction for die activity, and, in accordance with a determination that there is an error with the transaction parameters, the electronic device displays, on the display, an error notification (e.g., 708( ) indicating that an error has been detected. In some examples, while displaying the instructions (e.g., 906A) to activate a hardware button of the electronic device to authorize payment for the transaction, the electronic device forgoes displaying the respective additional transaction parameter.
{02611 Note that details of the processes described above with respect to method 10ÖÖ (e.g., FIG. 10) are also applicable in an analogous manner to the methods described above. For example, method 800 optionally includes one or more of the characteristics of the various methods described above with reference to method 1.000. For example, transaction user interface 706 described with reference to FIGS. 7A-7O and FIG. 8 is, in some examples, analogous to the
DK 2016 70622 A1 transaction user interface 906 described with reference to FIGS. 9A-9N an FIG. 10. For brevity, these details are not repeated below.
(0262] In accordance with some embodiments, FIG. Π shows an exemplary functional block diagram of an electronic device 1100 configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of tbe electronic device 1100 are configured to perforin the techniques described above. The functional blocks of the device 1100 are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG . I I are, optionally, combine-dor separated into sab-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.
{1)263( As shown in FIG. 11, an electronic device 1100 includes a display unit 1102 configured to display a graphic user interface, one or more input device units 1104, a hardware button unit 1108, and a processing unit 1106 coupled to the display unit 1102 , the one or more input device units 1104, and the hardware button unit 1108. Jn some embodiments, the processing unit 1106 includes a display enabling unit 1110, a detecting unit 1112, a receiving unit 1114, a proceeding unit. '1116, a monitoring unit 1118, a modifying unit 1120, and a selecting unit 1122.
(0264( The processing unit 1106 is configured to: enable display (e.g,, using the display enabling unit 1110), on the display unit 1102, of an application user interface for a respective application, wherein the application user interlace includes a transaction affordanee for requesting payment for activity associated with the respecti ve application; while enabling display of ihe application user interface, detect (e.g., using the detecting unit 1112), via the one or more input device units t .104, selection of the transaction affordanee; and in response to detecting selection of the transaction affordanee, enable display (e.g., using the display enabling unit 1110), on the display unit 1102, ofa transaction user interface that includes concurrently displaying: transaction details for the activity associated with the respective application; and
DK 2016 70622 A1 instructions to activate foe hardware button uni t 1108 of foe elec tronic device 1100 to authorize payment for the activity associated with the respective application.
[0265] In accordance with some embodiments, the transaction affordance displayed in the user interface for the respective application is provided by a payment application ofthe electronic device .1.100 that is different from the respective application.
[0266] in accordance with some embodiments, the transaction affordance that, when activated, triggers display of the transaction user interface, is provided by the respective application, in accordance with some embodiments, the respective application is a third-party application.
[0267] in accordance with some embodiments, the activity associated with the respective application includes one or more of: a request for transportation, a request for ride sharing, purchasing a service, purchasing a product, and conducting a peer-to-peer transaction.
[0268] in accordance with some embodiments, the transaction details include information about a cost of foe acti ity. in accordance with some embodiments, in accordance with a determination that the activity' has a variable cost, the transaction details include an indication, that foe activity has a variable cost.
[0269] in accordance with some embodiments, displaying the transaction user interlace further includes displaying a graphical representation of a payment account wi th which payment wall he made if authorization to proceed with the payment transaction is received, [0270] in accordance with some embodiments, foe processing unit 1106 is further configured to: while displaying foe transaction user interface that includes the transaction details and the instructions to activate the hardware button unit 1108, receive input (e.g., using the receiving unit 1114), via the one or more input device units 1104, corresponding to an instruction to scroll the transaction user interface; and in response to receiving the input corresponding to the instruction to scroll foe transaction user interface: enable display (e.g., on the display enabling unit 1110), on foe display unit 1102, o f additional transaction details for the activity associated with the respective application.
DK 2016 70622 A1 [0271] in accordance with some embodiments, the instructions to activate the hardware button unit 1108 are displayed at a location on the display unit 1102 that is determined based on a location of the hardware button unit 1108; displaying additional transaction details for the activity associated with the respective application includes; foregoing scrolling the instructions to activate the hardware button unit 1108; and scrolling the additional transaction details onto the display unit 1102,
JÖ272] In accordance with some embodiments, displaying additional transaction details for the activity associated with the respective application includes; scrolling the additional transaction details onto the display unit 1102 such that the additional transaction details obscure the instructions to activate the hardware button unit 1108.
|0273| In accordance with some embodiments, the processing unit 1106 is further configured to: while displaying tbe additional transaction details, detect (e.g., using tbe detecting unit 1112), via tbe one or more input device units 1104, selection of a first detail of the additional transaction details; and in response to detecting selection of the first detail of the additional transaction details, enable display fe.g., using tbe display enabling unit 1110), on the display unit 1102, of one or more options for tbe first detail.
(02-74] In accordance with some embodiments, the processing unit 1106 is further configured to; in accordance with the transaction user interface being displayed; monitor (e.g., using tbe monitoring unit 1118) the hardware button unit for activation; detect (e.g., using the detecting unit 1112) activation of the hardware button unit; and in response to detecting activation of the hardware button unit 1108, in accordance with a determinat ion that the act ivat ion of the hardware button unit 1108 meets transaction authorization criteria, proceed (e.g., using tbe proceeding unit 1116) with a transaction for the activity.
[0275] In accordance with some embodiments, the processing unit 1106 is further configured to; detect (e.g., using the detecting unit 1112) activation of the hardware button unit 1108; and in response to detecting activation of the hardware button unit 1108; in accordance with a determination that transaction processing criteria have been met, including a criterion that there is no error with the transaction parameters, proceed (e.g., using the proceeding unit 1116) with a transaction for the activity; and in accordance with a determination that there is an error with the
DK 2016 70622 A1 transaction parameters, enable display {e.g., using the display enabling unit 1110), on the display unit 1102, of an error notification indicating that an error has been detected instead of proceeding with the transaction, (0276( In accordance with some embodiments, the precessing unit J J 06 is further configured to: in accordance with the determination that there is an error with the transaction parameters, receive user input (e.g,, using the receiving unit 1114), via the one or more input device units 1104, at the electronic device .1.100; and in response to receiving the user input at the electronic device 3 300, modify the transaction parameters based on the user input.
(0277( hi accordance with some embodiments, the processing unit 1106 is further configured to: in accordance with the determination that there is an error with the transaction parameters, receive (e.g., using the receiving unit 1114) a request to correct the error; and in response to receiving the request to correct the error: in accordance with a determination that potentially compatible transaction parameters are available on the electronic device 1100, enable display (e.g., using the display enabling unit 1110), on the display unit 1102, of one or ntore of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the electronic device 13 00, enable display te.g., using the display enabling unit 1110), on the display unit 1102, of instructions to enter additional transaction parameters on a companion device that is different from the electronic device 1100, (0278( In accordance with some embodiments, displaying, on the display unit 1102, the error notification indicating that an error has been detected includes: replacing display of the instructions to activate the hardware button unit with display of the error notification, (0279( In accordance with some embodiments, the processing unit 1106 is further configured to: receive user input (e.g., using the receiving unit 1114), via the one or more input device units 1104, corresponding to an instruction to select a payment account from among a plurality of payment accounts of an electronic wallet of the electronic device 1100; and in response to detecting the user input corresponding to the instruction to select the payment account from among a plurality of payment accounts, select the payment account for use in the transaction for the activity.
DK 2016 70622 A1 [0280] In accordance with some embodiments, displaying the transaction user interlace includes replacing a displayed system user interface element with an indication of payment.
[028.1] In accordance with some embodiments, proceeding with the transaction for the activity includes: requesting a passcode', detecting, via the one or more input device units 1104, the passcode; and transmitting the passcode for processing the transaction.
[0282 j The operations described above with reference to FIG. 8 are, optionally, implemented by components depicted in FIGS. 1Α-Γ8 or FIG. 11. For example, displaying operation 802 and detecting operation 804 are, optionally, implemented by event sorter I70, event recognizer 180, and event handler .190. Event monitor .17.1 in event sorter 170 detects a contact on touchsensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation, of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer .180 activates an event handler 190 associated with the detection of the event or sub-event. Event handier 190 optionally utilizes or calls data -updater 176 or object updater 177 to update the application internal state 192, In some embodiments, event handier 190 accesses a respective GUI updater 178 to update what is displayed by fhe application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A~IB, [0283j in accordance with some embodiments, FIG 12 shows an exemplary functional block diagram of an electronic device 1200 configured in accordance with the principles of die various described embodiments. In accordance with some embodiments, the functional blocks of the electronic device 1200 are configured to perforin the techniques described above. The functional blocks ofthe device 1200 are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles ofthe various described examples, it is understood by persons of skill in the art that the functional blocks described in FIG. .12 are, optionally, combined or separated into sub-blocks to implement the principles ofthe various
DK 2016 70622 A1 described examples. Therefore, the description herein optionally supports any possible combination or separation or farther definition of the functional blocks described herein.
[0284] As shown in FIG. 12, an electronic device 1200 includes a display unit 1202 configured to display a graphic user interface, one or more input device units 1204, optionally, a hardware button unit 1208, optionally, a microphone unit 1224, and a processing unit 1206 coupled to the display unit 1202, the one or more input device units 1204, optionally, the hardware button unit 1208, and. optionally, the microphone unit 1224. In some embodiments, the processing unit .1206 includes a display enabling unit 1210, a detecting unit 1212, a receiving unit 1214, a proceeding unit 1216, a monitoring unit 12.1 S, a transmitting unit 1220, and an updating unit 1222.
[0285) The processing unit 1206 is configured to: receive (e.g., using the receiving unit 1214} a request to proceed with a transaction using transaction parameters; in response to the request to proceed with the transaction, in accordance with a. determination that there is an error with the transaction parameters, enable display (e.g., using the display enabling unit .12.10}, on the display unit 1202, of an error notification indicating that an error has been detected; receive {e.g., using the receiving unit 12.14), via the one or more input device units 1204, a request to correct the error; and in response to receiving the request, to correct the error: in accordance with a determination that potentially compatible transaction parameters are available on the electronic device 1.200, enable display (e.g,, using the display enabling unit 1210), on the display unit. I.202, of one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the electronic device 1200, enable display (e.g,, using the display enabling unit 1210), on the display unit 1202 , of instructions to enter additional transaction parameters on a companion device that is different from the electronic device 1200.
In accordance with some embodiments, the processing unit 1206 is further configured to, in response to the request to proceed with the transaction, in accordance with a determination that transaction processing criteria have been met, including a criterion that there was no error with the transaction parameters, proceed (e.g,, using the proceeding unit 1216) witli the transaction.
DK 2016 70622 A1 [0287] in accordance with some embodiments, the processing unit 1206 is further configured to; transmit (e.g., using the transmitting unit 1218), to the companion device, a request regarding a transaction parameter entry user interface; and wherein the companion device displays an indication o f the request regarding the transaction parameter entry user interface.
[0288] In accordance with some embodiments, activation, on the companion device, of the indication of the request regarding the transaction parameter entry user interface causes display, on a display unit of the companion device, of the transaction parameter entry user interface.
]0289j in accordance with some embodiments, the processing unit 1206 is further configured to: receive (e.g,, using the receiving unit 1214) a. respective additional transaction parameter; and in response to receiving the respective additional transact ion parameter, update (e.g., using the updating unit 1222) the transaction user interface in accordance with the respective additional transaction parameter, on the display unit 1202.
{0290) In accordance with some embodiments, tire processing unit 1206 is further configured to; in response to receiving the transaction parameter, update (e.g., using fhe updating unit 1222) the transaction parameters to include the respective additional transaction parameter tor use in the transaction.
{0291j In accordance with some embodiments, the processing unit 1206 is further configured to; in response to receiving the respective additional transaction parameter, enable display (e.g., using the display enabling unit 1.21.0), on the display unit 1202, of an indication of the respective additional transaction parameter; and while displaying the indication of the respective additional transaction parameter, detect (e.g., using the detecting unit 1212) activation of a hardware button unit 1208 of the electronic device 1200; and in accordance with a determination that there is no error with the updated transaction parameters that include the respective additional transaction parameter, proceed (e.g., using the proceeding unit 1216) with the transaction for the activity; and in accordance with a determination that there is an error with the updated transaction parameters, enable display (e.g., using the display enabling unit 1210), on the display unit 1202, of a second error notification indicating that an error has been detected.
DK 2016 70622 A1 (02921 In accordance with some embodiments, the processing unit 1206 is further configured to: in response to receiving the respective additional transaction parameter, enable display (e.g., using the display enabling unit 1210), on the display unit 1202, of instructions to activate a hardware button unit 1208 of the electronic device 1200 io authorize payment for the transaction; detect (e.g,, using foe detecting unit 1212) activation of the hardware button unit 1208; and In response to detecting activation of foe hardware button unit 1208: in accordance with a determination transaction processing criteria have been met, including a criterion that there is no error with foe updated transaction parameters, proceed (e.g., using the proceeding unit 1216) with a transaction for the activity; and in accordance with a determination that there is an error with the transaction parameters, enable display (e.g., using the display enabling unit 1210), on the display unit 1202, of an error notification indicating that an error has been .detected, (0293] in accordance with some embodiments, the processing unit 1206 is further configured to: in response to the request to proceed with the transaction, in accordance with the determination that there is an error with the transaction parameters, update (e.g., using the updating unit 1222) a displayed characteristic ofa displayed user interlace element to indicate that the error has been detected.
(0294( in accordance with some embodiments, the processing unit 1206 is further configured to: in response to receiving the request to correct the error: tn accordance with the determination that potentially compatible transaction parameters are available on the electronic device 1200: update (e.g., using the updating unit 1222) foe transaction parameters to include a default transaction parameter of the potentially compatible transaction parameters for use in the transaction; and enable display (e.g,, using the display enabling unit 1210), on the display unit 1202, of one or more affordances corresponding to one or more respective potentially compatible transaction parameters.
(0295
In accoidance wnh some embodiments, the processing nun
2<!is furthet coufiguied to: in response to receiving the request to correct the error; tn accordance with the determination that potentially compatible transaction .parameters are available on the electronic device 1200; enable display (e.g., using the display enabling unit 1210), on foe display unit 1202, of an entry'
DK 2016 70622 A1 affordance, which when activated, enables the user to provide a transaction parameter at the electronic device 1200, that is not included in the potentially compatible transaction parameters.
[0296] In accordance with some embodiments, the processing unit 1206 is further configured to; detect (e.g., using the detecting unit 1212) activation of the entry affordance; in response to detecting activation of entry affordance, monitor (e.g., using the monitoring unit 1218) audio input received via a microphone unit 1224 of the electronic device 1200; and update (e.g., using the updating unit 1222} the transaction parameters based on the audio input detected via the microphone unit 1224 of the electronic device 1200.
[0297] in accordance with some embodiments, the processing unit 1206 is further configured to; detect (e.g., using the detecting unit 1212) activation of the entry affordance; in response to detecting activation of entry affordance, enable display (e.g., using the display enabling unit 1210), on the display unit 1202, of one or more contacts based on contacts stored in a contacts application; receive (e.g,, using the receiving unit 1214} selection of a contact of the one or more contacts; and update (e.g., using the updating unit 1222) the transaction parameters based on the selected contact, [0298] In accordance with some embodiments, the processing unit 1206 is further configured to; detect te g, using the detecting unit) actuation of the entry affordance. tn response to detecting activation of entry affordance, transmit (e.g. , using the transmitting unit 1220), to the companion device, a second request regarding a second transaction parameter entry user interfece; and wherein the companion device displays a second indication of the request regarding foe second transaction parameter entry user interlace, [0299] S'be operations described aboxe w ith reietence ro HG. 10 ate. optionalis.
implemented by components depicted in FIGS. 1A-1B or FIG. 12. For example, receiving operation 1002 and displaying operation 1004 are, optionally, implemented hy event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or
DK 2016 70622 A1 sub event, such as activation ofan affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handier 190 optionally utilizes or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, e vent handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1 A-l B, (0300) Exemplary methods, devices, electronic· devices, computer-readable storage media and non-transitory computer-readable storage media are set out in the following items;
1. A method, comprising;
at an electronic device with a display, one or more input devices, and a hardware button; displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity associated with the respective application;
while displaying the application user interlace, detecting, via the one or more input devices, selection of the transaction affordance; and in response to detecting selection of the transaction affordance, displaying a transaction user interface that includes concurrently displaying.' transaction details for tire activity associated with the respective application; and instructions to activate the hardware button of the device to authorize payment for the activity associated with the respecti ve application.
2. The method of item 1, wherein the transaction affordance displayed in the application user interface for the respecti ve application is provided by a payment application of the electronic device drat is different from the respective application.
3. I'he method of any of items 1 - 2. wherein the transaction affordance that, when activated, triggers display of the transaction user interface, is provided by the respective application
DK 2016 70622 A1
4, The method of any of stems 1 - 3, wherein the respective application is a third-party application.
5. The method of any of items 1 -4, wherein the activity associated with the respective application includes one ot more of; a request for transportation, a request for tide sharing, purchasing a service, purchasing a product, and conducting a peer-to-peer transaction,
6. The method of any of items 1-5, wherein the transaction details include information about a cost of the activity.
7. The method of any of items 1 - ό. m accordance with a determination that the activity has a variable cost, the transaction details include an indication that the activity lias a variable cost.
8. The method of any of items 1-7, wherein displaying the transaction user interface further includes displaying a graphical representation of a payment account with which payment will he made if authorization to proceed with the payment transaction is received,
9. The method of any of items 1 - 8, further comprising:
while displaying the transaction user interface that includes the transaction details and the instructions to activate the hardware button, receiving input, via the one or more input devices, corresponding to an instruction to scroll the transaction user .interface; and in response to receiving the input corresponding to the instruction to scroll the transaction user interface:
displaying additional transaction details for the acti vity associated with the respective application.
10. The method of hem 9. wherein:
the instructions to activate the hardware button are displayed at a location on the display that is determined based on a location of the hardware button;
displaying additional transaction details for the activity associated with the respective application includes:
DK 2016 70622 A1 foregoing scroOing the instructions to activate the hardware button; and scrolling the additional transaction details onto the display,
1.1. Tlie method of item 9, wherein displaying additional transaction details for the activity associated with the respective application, includes·.
scrolling the additional transaction details onto the display such that the additional transaction details obscure the instructions to activate the hardware button.
12. The method of any of items 9 - 11. further comprising:
while displaying the additional transaction details, detecting, via. the one or more input devices, selection of a first detail of the additional transaction details; and in response to detecting selection of the first detail of the additional transaction details, displaying one or more options for the first detail.
13. The method of any of items f - 12, further comprising:
in accordance with the transaction user interface being displayed.' monitoring the hardware button for activation; detecting activation of the hardware button; and in response to detecting acti vation of the hardware button, in accordance with a detennination that the activation of tire hardware button meets transaction authorization criteria, proceeding with a transaction for the activity,
14. The method of any of tfems 1-13. further comprising:
detecting activation of the hardware button; and in. response to detecting activation of the hardware button:
in accordance with a determination that transaction processing criteria have been met, including a criterion that, there is no error with the transaction parameters, proceeding with a transaction for the activity; and.
in accordance with a determination that there is an error with, the transaction parameters, displaying, on the display, an error notification indicating that an error has been detected instead of proceeding with the transaction.
DK 2016 70622 A1
15. The method of item 14, liirther comprising.
in accordance with the determination that there is an error with the transaction parameters, receiving user input, via the one or more input devices, at the electronic device; and in response to receiving the user input at the electronic device, modifying the transaction parameters based on the user input.
16. The method of item .14, further comprising:
in accordance with the determination that there is an error with the transaction parameters., receiving a request to correct the error; and in response to receiving the request to correct the error:
in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the electronic device, displaying instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
17. The method of any of items 14 -16, wherein displaying, on the display, the error notification indicating that an error has been detected includes:
replacing display of the instructions to activate the hardware button with display of the error notification.
18. The method of any of items 1 - 17, further comprising:
receiving user input, via the one or more input devices, corresponding to an instruction to select a payment account from among a plurality of payment accounts of an electronic wallet of the electronic device; and in response to detecting the user input corresponding to the instruction to select the payment account from among a plurality of p ayment accounts, selecting the payment account for use in the transaction tor the activity.
100
DK 2016 70622 A1
19, The method of any of items 1 - 18, wherein displaying the transaction user interface includes replacing a displayed system user interface element with an indication of payment,
20. The method of any of item« 14-19 wherein proceeding with the transaction for the activity includes: requesting a passcode;
detecting, via the one or more input devices, the passcode: and transmitting the passcode for processing the transaction.
21. A computer-readable storage medium storing one or more programs configured to he executed by one or more processors of an electronic device with a display, one or more input devices, and a hardware button, the one or more programs including instructions for perfonning the method of any of items 1 - 20,
22, An electronic device, comprising:
a display;
one or more input devices;
a hardware button;
one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any of hems 1 - 20,
23, An electronic device, comprising: a display;
one or more input devices; a hardware button; and means tor performing the method of any of items 1 - 20,
24. A non-transitory computer-readable storage medium, storing one or more programs configured to be executed by one or more processors of an electronic device with a display, one
101
DK 2016 70622 A1 or more input devices, and a hardware button, the one or more programs including instructions for;
displaying, on foe display, an application user interlace for a respective application, wherein foe application user interlace includes a transaction affordance for requesting payment for activity associated with the respective application;
while displaying the application user interface, detecting, via the one or more input devices, selection ofthe transaction affordance; and in response to detecting selection of the transaction affordance, displaying a transaction user interface that includes concurrently displaying;
transaction details for the activity associated with, the respective application; and instructions to activate the hardware button of the device to authorize payment for the activity associated with the respective application,
25. An electronic device, comprising;
one or more input devices;
a hardware button;
one or more processors; and a memory storing one or more programs configured to he executed hy the one or more processors, the one or more programs including instructions for;
displaying, on foe display, an application user interlace for a respective application, wherein the application user interface includes a transaction affordance for requesting payment lor activity associated with foe respective application;
while displaying the application user interlace, detecting, via the one or more input devices, selection ofthe transaction affordance; and in response to detecting selection of foe transaction affordance, displaying a transaction user interface that includes concurrently displaying;
transaction details for foe activity associated with the respective application; and
102
DK 2016 70622 A1 instructions to activate the hardware button of the device to authorize payment for the activity associated with the respective application.
26. An electronic device, comprising:
adisplay;
one or more input devices; a hardware button;
means for displaying, on the display, an application user interface for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity' associated with the respective application;
means, while displaying the application user interface, for detecting, via the one or more input devices, selection of the transaction affordance; and means, responsive to detecting selection of the transaction affordance, for displaying a transaction user interlace that includes concurrently displaying:
transaction details for the activity associated with the respective application; and instructions to acti vate the hardware button of the device to authorize pay ment for the activity associated with the respective application.
27. A method, comprising:
at an electronic device with a display and one or more input devices:
receiving a request to proceed with a transaction using transaction parameters; in response to the request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters, displaying an error notification indicating that an error has been detected;
receiving, via the one or more input devices, a request to correct the error; and in response to receiving the request to correct the error:
in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on the display, one or more of the potentially compatible transaction parameters; and in. accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter
103
DK 2016 70622 A1 additional transaction parameters on a companion device that is different from the electronic device.
28, The method of item 27, further compri sing, in response to the request to proceed with fhe transaction, in accordance with a determination that transaction processing catena have been met, including a criterion that there was no error with the transaction parameters, proceeding with the transaction.
29, The method of any of items 27 - 28, further comprising:
transmitting, to foe companion device, a request regarding a transaction parameter entry user interface; and wherein the companion device displays an indication of the request regarding the transaction parameter entry user interface,
30, The method of item 29, wherein activation, on the companion device, of fhe indication of the request regarding the transaction parameter entry' user interface causes display, on a display of the companion device, of foe transaction parameter entry' user interface.
31. The method of any of items 27 - 30, further comprising:
receiving a respective additional transaction parameter; and in response to receiving foe respective additional transaction parameter, updating a transaction user interface in accordance with the respective additional transaction parameter, on the display32. The method of item 31, further comprising:
in response to receiving the transaction parameter, updating the transaction parameters to include the respective additional transaction parameter for use in foe transaction.
33. The method of any o f items 31 - 32, further comprising;
in response to receiving the respective additional transaction parameter, displaying, on the display, an indieationof foe respective additional transaction parameter; and
104
DK 2016 70622 A1 while displaying the indication of the respective additional transaction parameter, detecting activation ofa hardware button of the electronic device; and in accordance with a determination that there is no error with the updated transaction parameters that include the respective additional transaction parameter, proceeding with the transaction for the activity; and in accordance with a determination that there is an error with the updated transaction parameters, displaying, on the display, a second error notification indicating that an error has been detected,
34. Täte method of any of items 31 ~ 33, further comprising:
in response to receiving the respective additional transaction parameter, displaying, on the display , instructions to activate a hardware button of the electronic device to authorize payment for the transaction;
detecting activation o f tire hardware button; and in response to detecting activa tion of foe hardware button:
in accordance with a determination that transaction processing criteria have been met, including a criterion that there is no error with the updated transaction parameters, proceeding with a transaction for the activity; and in accordance with a determination that there is an error with the transaction parameters, displaying, on the display, an error notification indicating that an error has been detected.
35. The method of any of items 27 - 34. further comprising:
in response to the request to proceed with the transaction, in accordance with the determination that there is an error with the transaction parameters, updating a displayed characteristic of a displayed user interface element to indicate that foe error has been detected,
36. The method of any of items 27 - 35, further comprising:
in response to receiving the request to correct the error:
in accordance with the determination that potentially compatible transaction parameters are available on the electronic device;
105
DK 2016 70622 A1 updating foe transaction parameters to include a default transaction parameter ofthe potentially compatible transaction parameters for use in the transaction; and displaying, on the display, one or more affordances corresponding to one or more respective potential ly compatible transaction parameters,
37. The method of item 36, further comprising;
in response to receiving the request to correct tire error:
in accordance with the determination that potentially compatible transaction parameters are available on the electronic device:
displaying, on the display, an entry affordance, which when activated, enables foe user to provide a transaction parameter at the electronic device, that is not included in foe potentially compatible transaction parameters.
38. The method of item 37, further comprising:
detecting activation of foe entry·' affordance:
in response to detecting activation of entry affordance, monitoring audio input received via a microphone ofthe electronic device; and updating the transaction parameters based on the audio inpot received via foe microphone of the electronic device.
39. The method of any of items 37 ~ 38, further comprising:
detecting activation ofthe entry affordance;
in response to detecting activation of entry affordance, displaying one or more contacts based on contacts stored in a contacts application:
recei ving selection of a contact of foe one or more contacts; and updating the transaction parameters based on the selected contact.
40. The method of any of items 37 - 39, further comprising;
detecting activation of the entry affordance;
in response to detecting activation of entry affordance, transmitting, to the companion device, a second request regarding a second transaction parameter entry user interlace; and
106
DK 2016 70622 A1 wherein foe companion device displays a second indication of foe request regarding foe second transaction parameter entry user interface.
41. A computer-readable storage medium storing one or more programs configured to he executed by one or more processors of an electronic device with a display and one or more input devices, the one or more programs including instructions for performing the method of any of items 27-40.
42. An electronic device, comprising:
a display;
one or more input devices; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any of items 27 ~ 40.
43, An electronic device, comprising:
a display;
one or more input devices; and means for performing foe method of any of items 27 - 40.
44. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device wi th a display and one or more input devices, fhe one or more programs including instructions for:
receiving a request to proceed with a transaction using transaction parameters; in response to the request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters, displaying an error notification indicating that an error has been detected;
receiving, via the one or more input devices, a request to correct the error; audio
DK 2016 70622 A1 in response to receiving the request to correct the error;
in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on the display, one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
45. An electronic device, comprising:
one or more input devices; one or more processors; and a memory storing one or more programs configured to be executed hy the one or more processors, the one or more programs including instructions for:
receiving a request to proceed with a transaction using transaction parameters; in response to the request to proceed with the transaction, in accordance witli a determination that there is an error with the transaction parameters, displaying an error notification indicating that an error has been detected;
receiving, via the one or more input devices, a request to correct the error; and in response to receiving the request to correct the error;
in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on the display, one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
46, An e‘<. ironic device, comprising:
108
DK 2016 70622 A1 one or more input devices;
means for receiving a request io proceed with a transaction using transaction parameters;
means, responsive to the request to proceed with the transaction, in accordance: with a determination that there is an error with the transaction parameters, for displaying an error notification indicating that an error has been detected;
means for receiving, via the one or more input devices, a request to correct the error; and means, responsive to receiving the request to correct the error, for:
in accordance wife a determination that poten ti ally compatible transaction parameters are available on the electronic device, displaying, on the display, one or more of the potential ly compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the eieetronie device.
47. An electronic device, comprising:
a display unit, one or more input device units;
a hardware button unit; and a processing unit coupled to the display uni t, the one or more input device units, and the hardware button unit, the processing unit configured to:
enable display, on the display unit, of an application user interlace for a respective application, wherein the application user interface includes a transaction affordance for requesting payment for activity associated with the respective application;
while enabling display of the application user interface, detect, via the one or more input device uni ts, selection of the transaction affordance; and in response to detecting selection of the transaction affordance, enable display, on the display unit, of a transaction user interface that includes concurrently displaying;
transaction details for the activity associated with the respective application; and
109
DK 2016 70622 A1 instructions to activate the hardware button unit of the electronic device to authorize payment for the activity associated with the respective application.
The electronic desice of stem -P wherein the transaction affordance displaced m the application user interface for the respective application is provided by a payment application of the electronic device that is different from the respective application.
49. The electronic device of any of items 47 - 48, wherein the transaction affordance that, when activated, triggers display of the transaction user interface, is provided by the respective application,
50. The electronic device of any of items 47 ~ 49, wherein the respective application, is a. thirdparty application.
51. The electronic device of any of items 47 - 50, wherein the activity associated with the respective application includes one or more of: a request for transportation, a request for ride sharing, purchasing a sendee, purchasing a product, and conducting a peer-to-peer transaction.
52. The electronic device of any of items 47 - 51, wherein the transaction details include infonnaiion about a cost of the activity,
53. The electronic device of any of items 47 - 52, in accordance with a determination that the activity has a variable cost, the transaction details include an indication that the activity has a variable cost,
54. The electronic device of any of items 47 - 53, wherein displaying the transaction user interlace further includes displaying a graphical representation of a payment account with which payment will be made if authorization to proceed with the payment transaction is received.
55. The electronic device of any of items 47 - 54, wherein the processing unit is lurther configured to:
no
DK 2016 70622 A1 while displaying the transaction user interlace that includes the transaction details and fhe instructions to activate the hardware button unit, receive input, via the one or more input device units, corresponding to an instruction to scroll the transaction user interface; and in response to receiving the input corresponding to the instruction to scroll the transaction user interface;
enable display, on the display unit, of additional transaction details for the activity associated with the respective application.
56. The electronic device of item 55, wherein:
the instructions to activate the hardware button unit are displayed at a location on the display unit that is determined based on a location of the hard ware button unit;
displaying additional transaction details for the activity associated with the respective application includes:
foregoing scrolling the instructions to activate the hardware button unit; and scrolling the additional transaction details onto the display unit,
57. The electronic device of item 55, wherein displaying additional transaction details for the activity associated with the respective application includes;
scrolling the additional transaction details onto the display unit such that the additional transaction details obscure fhe instructions to activate fhe hardware button unit.
58, Tlie electronic device of any of items 55 - 57, wherein the processing unit is further configured to:
while displaying the additional transaction details, detect, via the one or more input device units , selection of a first detail of the additional transaction details; and in response to detecting selection of the first detail of the additional transaction details, enable display, on the display unit, of one or more options for the first detail.
59. The electronic device of any of items 47 - 58, wherein the processing unit is further configured to;
in accordance with fhe transaction user interface being displayed.'
Ill
DK 2016 70622 A1 monitor the hardware button unit for activation; detect activation of the hardware button unit; and in response to detecting activation of the hardware button unit, in accordance with a determination that the activation of foe hardware button unit meets transaction authorization criteria, proceed with a transaction for the activity'.
The electronic device of any' of items 47 - 59. wherein the processing umt ts further configured to;
detect activation of the hardware button unit; and in response to detecting activation of the hardware button unit;
in accordance with a determination that transaction processing criteria have been met, including a criterion that there is no error with the transaction parameters, proceed with a. transaction for the activity· and in accordance with a determination that there is an error with tbe transaction parameters, enable display, on foe display unit, of an error notification indicating that an error lias been detected Instead of proceeding with the transaction.
61. The electronic device of item 60, wherein the processing unit is further configured to: in accordance with the determination that there is an error with the transaction parameters, receive user input, via the one or more input device units, at the electronic device; and in response to receiving the user input at the electronic device, modify the transaction parameters based on foe user input,
62. The electronic device of item 60, wherein the processing unit is further configured to in accordance with foe determination that there is an error with the transaction parameters, recei ve a request to correct, the error; and in response to receiving the request to correct the error:
in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, enable display, on foe display unit, of one or more of the potentially compatible transaction parameters; and
112
DK 2016 70622 A1 in accordance with a determination drat potentially compatible transaction parameters are not available on tire electronic device, enable display, on the display unit, of instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
63. The electronic device of any of items 60 - 62, wherein displaying, on the display unit, die error notification indicating that an error has been detected includes;
replacing display of the instructions to activate the hardware button unit with display of the error notification.
64. I he electronic device of any of items 47 - 63. wherein the processing unit is further configured to;
receive user input, via the one or more input device units, corresponding to an instruction to select a payment account from among a plurality of payment accounts of an electronic wallet ofthe electronic device', and in response to detecting the user input corresponding to the instruction to select the payment account from among a plurality of payment accounts, select the payment account for use in the transaction for the activity.
65. The electronic device of any of items 47 - 64, wherein displaying the transaction user interlace includes replacing a displayed system user interface element with an indication of payment.
66. The electronic device of any of items 60 - 65, wherein:
proceeding with the transaction for the activity includes: requesting a passcode;
detecting, via the one or more input device units, the passcode; and transmitting the passcode for processing the transaction,
67. An electronic device, comprising:
a display unit;
113
DK 2016 70622 A1 one or more input device units; and a processing unit coupled to the display unit and the one or more input device units, the processing unit configured to;
receive a request to proceed with a transaction using transaction parameters; in response ίο the request to proceed with the transaction, in accordance with a determination that there is tut error with the transaction parameters, enable display, on foe display unit, of an error notification indicating that an error has been detected;
receive, via the one or more input device units, a request to correct the error; and in response to receiving the request to correct the error;
in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, enable display, on the display uni t, of one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the electronic device, enable display, on the display unit, of instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
68. The electronic device of item 67. wherein the processing unit is further configured to; in response to the request to proceed with the transaction, in accordance with a determination that transaction processing criteria have been met, including a criterion that there was no error with the transaction parameters, proceed with the transaction.
69. The electronic device of any of items 67 - 68. wherein the processing unit is further configured to;
transmit, to the companion device, a request regarding a transaction parameter entry user interlace; and wherein the companion device displays an indication of the request' regarding the transaction parameter entry user interface.
IM
DK 2016 70622 A1
70, The electronic device of item 69, wherein acti.vaii.oir, on the companion device, of fee indicationof the request regarding fee transaction parameter entry user interface causes display, on a display unit of the companion device, of ihe transaction parameter entry user interface.
71, The electronic device of any of items 67 - 70, wherein the processing unit is further configured to;
receive a respective additional transaction parameter; and in response to receiving fee respective additional transaction parameter, update a transaction user interface in accordance with the respective additional transaction parameter, on fee display unit.
72, The electronic device of item 71, wherein the processing unit is further configured to;
in response to receiving fee transaction parameter, update the transaction parameters to include the respective additional transaction parameter for use in the transaction.
7.1. The electronic device of any of items 71 - 72, wherein the processing unit is further configured to;
in response to receiving the respective additional transaction parameter, enable display, on the display unit, of an indication of the respective additional transaction parameter; and while displaying fee indication of fee respective additional transaction parameter, detect activation, of a hardware button unit of the electronic device; and in. accordance with a deiernrination that there is no error with the updated transaction parameters that include the respective additional transaction parameter, proceed wife fee transaction for the activity; and rn accordance wife a determination that there is an error with the updated transaction parameters, enable display, on the dispiay unit, of a second error notification indicating that an error has been detected.
74. The electronic device of any of items 71 ~ 73, wherein fee processing unit is further configured to;
115
DK 2016 70622 A1 in response to receiving the respective additional transaction parameter, enable display, on the display unit, of instructions to activate a hardware button unit of the electronic device to authorize payment for the transaction;
detect activation of the hardware button unit; and in response to detecting activation of the hardware button unit;
in accordance with a determination transaction processing criteria have been met, including a criterion that there is no error with the updated transaction parameters, proceed with a transaction for the activity; and in accordance with a determination tliat there is an error with the transaction parameters,, enable display, on the display unit, of an error notification indicating that an error has been detected.
The electioniv device of ant of items o~ - 4. wiicieni the piece:
configured to;
in response to the request to proceed with the transaction, in accordance with the determination that there is an error with the transaction parameters, update a displayed characteristic of a displayed user interfece element to indicate that the error has been detected.
76, The eleeironic device of any of items 67 - 75, wherein the processing unit is further configured to;
in response to receiving the request to correct the error;
in accordance with the determination that potentially compatible transaction parameters are available on the electronic device:
update foe transaction parameters to include a default transaction parameter of the potentially compatible transaction parameters for use in the transaction; and enable display, on the display unit, of one or more affordances corresponding to one or more respective potentially compatible transaction parameters.
77. The electronic device of item 76, wherein the processing unit is further configured to: in response to receiving the request to correct the error:
116
DK 2016 70622 A1 in accordance with the determination that potentially compatible transaction parameters are available on the electronic device:
enable display, on the display unit, of an entry affordance, which when activated, enables the user to provide a transaction parameter at foe electronic device, that is not included in the potentially compatible transaction parameters.
The electronic device of item 77, wherein the processing umt ts further configured to: detect activation of the entry affordance:
in response to detecting activation of entry affordance, monitor audio input received via a microphone unit of the electronic device: and update the transaction parameters based on the audio input received via the microphone unit of the electronic device.
79. The electronic device of any of items 77 - 78. wherein ihe processing unit is further configured to:
detect activation of the entry affordance;
in response to detecting activation of entry affordance, enable display, on the display unit, of one or more contacts based on contacts stored in a contacts application;
recei ve se lection of a contact of fir e one or more contacts; and update the transaction parameters based on the selected contact.
80, Tire electronic device of any of items 77 - 79. wherein the processing unit is further configured to:
detect activation ofthe entry' affordance:
in response to detecting activation of entry affordance, transmit, to the companion device, a second request regarding a second transaction parameter entry user interface; and wherein the companion device displays a second indication of the request regarding the second transaction parameter entry user interface.
[0301| The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended
117
DK 2016 70622 A1 to he exhaustive or to limit the invention to foe precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and foeir practical applications, Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
[0302[ Although the disclosure and examples hav e been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
[0303j As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery' to users of invitational content or any other content that may ho of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.
[0304J The present disclosure recognizes that the use of such personal information data, m foe present technology, can be used to foe benefit of users. For example, foe personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content, Furfoer, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
[0305 j The present disclosure thither contemplates that foe entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices, in particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements tor maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside
118
DK 2016 70622 A1 of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access io such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.
(0306] Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can he provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal infbnnation data during registration for services, in another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.
{0307 ) Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without, the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered fo users by inferring preferences based on non-personal information data or a hare minimum amount of personal information, such as the content being requested by the device associated with a user, other nonpersonal information available fo the content delivery services, or publically available information.
119
DK 2016 70622 A1

权利要求:
Claims (23)
[1] 1. /A method, comprising;
at an electronic device with a display and one or more input devices;
receiving a request to proceed with a transaction using transaction parameters; in response to the request to proceed with the transaction, in accordance with a determination that there is an error with the transaction parameters, displaying an error notification indicating that an error has been detected;
receiving, via the one or more input devices, a request to correct the error; and in response to receiving the request to correct the error:
in accordance with a determination that potentially compatible transaction parameters are available on the electronic device, displaying, on the display, one or more of the potentially compatible transaction parameters; and in accordance with a determination that potentially compatible transaction parameters are not available on the device, displaying, on the display, instructions to enter additional transaction parameters on a companion device that is different from the electronic device.
[2] 2. The method of claim 1, further comprising;
in response to the request to proceed with the transaction, in accordance with a detennination that transaction processing criteria have been met, including a criterion that there was no error with the transaction parameters, proceeding with the transaction.
[3] 3. The method of any of claims 1-2, further comprising:
transmitting, to the companion device, a request regarding a transaction parameter entry user interface; and wherein the companion device displays an indication of the request regarding the transaction parameter entry user interface.
120
DK 2016 70622 A1
[4] 4. The method of claim 3, wherein activation, on the companion device, of the indication of the request regarding the transaction parameter entry user interlace causes display, on a display of the companion device, of the transaction parameter entry user interface,
[5] 5. The method of any of claims ί -4, further comprising:
receiving a respective additional transaction parameter; and in response to recei ving the respective additional transaction parameter, updating a transaction user interface in accordance with the respective additional transaction parameter, on the display.
[6] 6. The method of claim 5, further comprising:
in response to receiving the transaction parameter, updating the transaction parameters to Include the respective additional transaction parameter for use in the transaction.
[7] 7. The method of any of claims 5-6, thither comprising;
hi response to receiving the respective additional transaction parameter, displaying, on the display, an Indication of fhe respective additional transaction parameter; and while displaying the indication of the respective additional, transaction parameter, detecting activation of a hardware button of the electronic device: and in accordance with a determination that there is no error with the updated transaction parameters that include the respective additional transaction parameter, proceeding with the transaction for the activity; and in accordance with a determination that there ts an error with the updated transaction parameters, displaying, on the display, a second error notification indicating that an error has been detected.
[8] 8. I he method of any of claims 5-7, further comprising:
nt response to receistng the respective additional transaction parameter, displaying. on the display, instructions to activate a hardware button of the electronic device to authorize payment for the transaction;
detecting activation of the hardware button; and
121
DK 2016 70622 A1 in response to detecting activation of the hardware button;
in accordance with a determination that transaction processing criteria have been met, inchiding a criterion that there is no error with the updated transaction parameters, proceeding with a transaction for the activity; and in accordance with a determination that there is an error with the transaction parameters, displaying, on the display, an error notification indicating that an error has been detected.
[9] 9. The method of any of claims 1--S, further comprising;:
in response to the request to proceed with the transaction, in accordance with the determination that there is an error with the transaction parameters, updating a displayed characteristic of a displayed user interface element to indicate that the error has been detected.
[10] 10. The method of any of claims 1 -9, &rther comprising:
in response to receiving the request to correct the error:
in accordance with the determination that potentially compatible transaction parameters are available on the electronic device:
updating the transaction parameters to include a default transaction parameter of the potentially compatible transaction parameters for use in the transaction; and displaying, on the display, one or more affordances corresponding to one or more respective potentially compatible transaction parameters.
TI. The method of claim IO. further comprising:
in response to receiving the request to correct the error:
in accordance with the determination that potentially compatible transaction parameters are available on the electronic device:
displaying, on the display, an entry affordance, which when activated, enables the user io provide a transaction parameter at tire electronic device, that is not included m the potentially compatible transaction parameters.
12. The method of claim 11, further comprising:
122
DK 2016 70622 A1 detecting activation of the entry affordanee;
in response to detecting activation of entry affordanee, monitoring audio input received via a microphone of the electronic device; and updating the transaction parameters based on the audio input received via the microphone of the elec tronic device.
53. The method of any of claims 11-12, further comprising' detecting activation of the entry affordanee;
in response to detecting activation of entry' affordanee, displaying one or more contacts based on contacts stored in a contacts application;
receiving selection of a contact of the one or more contacts; and updating the transaction parameters based on the selected contact.
14. The method of any of claims 11-13, further comprising: detecting activation of the entry affordanee;
in response to detecting activation of entry affordanee, transmi tting; to the companion device, a second request regarding a. second transaction parameter entry user interface; and wherein, the companion device displays a second indication of the request regarding the second transaction parameter entry user interface.
15. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more input devices, the one or more programs including instructions for performing the method of any of claims 1-34.
16, An electronic device, comprising; a dispiav;
one or more input devices; one or more processors; and
123
DK 2016 70622 A1 memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any of claims I -14.
124
DK 2016 70622 A1
M
Memory 102
1/48
Portable Multifunction Device 100 ry- 136
148
Speaker
111
DK 2016 70622 A1
2/48 'S o
05^ g B a> Ξ£ c•g o ® «S <**
LU -~ ® fc: s£ ω
S-w-f **5·*
S < O
Φ
O 'S <x.
<2
O cS
0i >
LU
DK 2016 70622 A1
3/48
Microphone
113
204
External Port 124
DK 2016 70622 A1
4/48
Device 300
Operating System
S~
Memory 370Communication Module
Contact/Motion Module
Graphics Module
Haptic Feedback Module
I ext Input Modul«
Applications
Contacts Module
Telephone Module
Video Conference Module
-mail Client Module
Workout Support Module
Camera Module 'X
X
X
X
X
126
128
130
132
133
134 130
137
138
139
140
141
142
143
Factlle Output fsi ment Module rowser Module
Calendar Module
Widest Modules
Veatber Widget
Stocks Widget
Calculator Widget
Alarm Clock Widget
Dictionary Widget
User-Created Widget(s)
Wldoet Creator Module
Search Module
Video & Music Haver Module
Drawing Module
Presentation Module bensons) 359
Word Processing Module
Website Creation Module
Disk Authoring Module
Communications
Interface
Spreadsheet Module .X wX
X
X
X
X
147
143
149 149-1 149-2 149-3 149-4 149-5
149-6
150
151
152 330 332 334 386 388 390 **************************************************************************************
Device-Global Internal State
360
157
DK 2016 70622 A1
5/48 k F4
DK 2016 70622 A1
6/48 '^Xaa
DK 2016 70622 A1
7/48
DEVICE 500 ·
F/G 54
DK 2016 70622 A1
8/48
C4 ti.
DK 2016 70622 A1
9/48 '12
.... j o
INTENSITY
MEASUREMENT OF INTENSITY SENSOR
524Ä
INTENSITY MEASUREMENT OF INTENSITY
SENSOR
524B
INTENSITY MEASUREMENT OF INTENSITY
SENSOR
524C /
y
INTENSITY MEASUREMENT OF INTENSiTY
SENSOR
524D
DK 2016 70622 A1
10/48
524C
TOUCHSENSITIVE DISPLAY SCREEN ' 504
524B
CONTACT 552A ί
INTENSITY OF CONTACT
552B ~8 /
~y
INTENSITY OPCONTACT
552.D /
-/7 /
INTENSITY OF CONTACT
552E /
f
INTENSITY OPCONTACT
552C /76. 5Z>
DK 2016 70622 A1
[11] 11/48
570
DISPLAY >04
m.
)
INTENSITY OF
CONTACT
562
DK 2016 70622 A1
[12] 12/48
572B
Π'·)
IT ii
i.
i
INTENSITY OF
CONTACT
562
DK 2016 70622 A1
[13] 13/48
DISPLAY
504
S
5 (t
574
I'OUCH
SENSITIVE
SURFACE
560
5728
INTENSITY OF
CONTACT
562
DK 2016 70622 A1
[14] 14/48
--- % $ I j T ¹¹D
m.
’y~ rr_o
INTENSITY OF
CONTACT
562
DK 2016 70622 A1
[15] 15/48
DK 2016 70622 A1
18/48
500A /
.f
DK 2016 70622 A1
17/48
DK 2016 70622 A1
[16] 18/48 £/<£ 7C
-· 794B
DK 2016 70622 A1
[17] 19/48
-· 7943
DK 2016 70622 A1
[18] 20/48
706A
CANCEL
706B φ o
ΓΟ RIDE SHARE
PAY / / /-DOUBLE CLICK TO PA Y
AMEX
84B
DK 2016 70622 A1
[19] 21/48
DK 2016 70622 A1
[20] 22/48
DK 2016 70622 A1
[21] 23/48
C
706—_χ
7106CONTACT
PHÖNE (i23)456-7890
PAY
-· 7943 (555)555-5555
ADD ON COMPANION DEVICE
JOC
DK 2016 70622 A1
[22] 24/48
DK 2016 70622 A1
[23] 25/48
DK 2016 70622 A1
28/48
DK 2016 70622 A1
27/48
-· 7943
DK 2016 70622 A1
28/48
- 7948
DK 2016 70622 A1
29/48
DK 2016 70622 A1
30/48 'χ
C/ / vj
DOU BLE CLICK TO PAY
TO RIDE SHARE
PAY
704B
- 706A .--/06
706.B
AM EX
G) 7<
DK 2016 70622 A1
31/48
DK 2016 70622 A1
32/48 •Min
DK 2016 70622 A1
33/48
DK 2016 70622 A1
34/48
DK 2016 70622 A1
35/48
DK 2016 70622 A1
38/48
DK 2016 70622 A1
37/48
f...............................................................................................>PAY I ADDRESS UNAVAILABLE Km PLEASE GO TO TBE WATCH APPLICATIONON YOUR PHONE *_/ /
DK 2016 70622 A1
38/48
DK 2016 70622 A1
3/48
DK 2016 70622 A1
40/48 (>:·»
4/'
DK 2016 70622 A1
41 /48
F/G, 9J
DK 2016 70622 A1
42/48

类似技术:

---

公开号 | 公开日 | 专利标题

---

AU2017284013B2|2020-09-10|User interfaces for transactions

---

DK180005B1|2020-01-16|REMOTE AUTHORIZATION TO CONTINUE WITH AN ACTION

---

US10621581B2|2020-04-14|User interface for transactions

---

AU2017101375A4|2017-11-09|User interface for loyalty accounts and private label accounts for a wearable device

---

AU2016102031A4|2016-12-22|User interface for payments

---

AU2020273355B2|2022-01-27|User interfaces for transactions

---

WO2017218094A1|2017-12-21|User interfaces for transactions

---

AU2017100558A4|2017-06-29|User interface for transactions

---

US20210397681A1|2021-12-23|User interfaces for managing secure operations

---

WO2021262432A1|2021-12-30|User interfaces for accessing an account

同族专利:

---

公开号 | 公开日

---

EP3469536A4|2019-12-25|

---

AU2017284013A1|2018-12-13|

---

AU2017284013B2|2020-09-10|

---

EP3469536A1|2019-04-17|

---

US20170357973A1|2017-12-14|

---

US11037150B2|2021-06-15|

---

US20210272118A1|2021-09-02|

---

CN109219827A|2019-01-15|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

US20140372309A1|2002-07-15|2014-12-18|Chase Paymentech Solutions, Llc|System and apparatus for transaction data format and function verification|

---

US7454192B1|2005-02-04|2008-11-18|Sprint Communications Company, L.P.|Postal address validation using mobile telephone location information|

---

US20110106671A1|2009-10-30|2011-05-05|Bank Of America Corporation|Financial Transaction Error Detection|

---

US20110214158A1|2010-02-26|2011-09-01|Research In Motion Limited|Wireless communications system providing mobile device authentication bypass based upon user-wearable security device and related methods|

---

US20120024947A1|2010-07-29|2012-02-02|Bank Of America Corporation|Wearable article having point of sale payment functionality|

---

US20150229750A1|2011-07-18|2015-08-13|Andrew H B Zhou|Wearable personal digital device for facilitating mobile device payments and personal use|

---

US20150012435A1|2013-07-08|2015-01-08|Bharathi Ramavarjula|Bank account number validation|

---

US20150120545A1|2013-10-28|2015-04-30|Jpmorgan Chase Bank, N.A.|Non-compliant payment capture systems and methods|

---

WO2015062410A1|2013-10-29|2015-05-07|Tencent Technology Company Limited|Method and device for processing progressive response|

---

US20150195133A1|2014-01-07|2015-07-09|John Sheets|Methods and systems for provisioning multiple devices|

---

US20150242837A1|2014-02-21|2015-08-27|Ebay Inc.|Facilitating payments using wearable devices|

---

US20160012417A1|2014-07-14|2016-01-14|Mastercard International Incorporated|System and method for loading and reloading prepaid payment cards from mobile devices|

---

US20160034887A1|2014-07-31|2016-02-04|Lg Electronics Inc.|Wearable device and method for controlling the same|

---

US20160086176A1|2014-09-18|2016-03-24|Samsung Eletronica Da Amazonia Ltda.|Method for multi-factor transaction authentication using wearable devices|

---

US20160132864A1|2014-11-07|2016-05-12|Paypal, Inc.|Payment processing apparatus|

---

US5265007A|1988-06-07|1993-11-23|Huntington Bancshares Incorporated|Central check clearing system|

---

US5691524A|1991-07-17|1997-11-25|J.D. Carreker And Associates, Inc.|Electronic check presentment system having a non-ECP exceptions notification system incorporated therein|

---

US5237159A|1991-07-17|1993-08-17|J. D. Carreker And Associates|Electronic check presentment system|

---

US5484988A|1992-11-13|1996-01-16|Resource Technology Services, Inc.|Checkwriting point of sale system|

---

JPH06284182A|1993-03-30|1994-10-07|Fujitsu Ltd|Portable telephone set|

---

US6269348B1|1994-11-28|2001-07-31|Veristar Corporation|Tokenless biometric electronic debit and credit transactions|

---

US6230148B1|1994-11-28|2001-05-08|Veristar Corporation|Tokenless biometric electric check transaction|

---

US6950810B2|1994-11-28|2005-09-27|Indivos Corporation|Tokenless biometric electronic financial transactions via a third party identicator|

---

US5717868A|1995-03-07|1998-02-10|Huntington Bancshares Inc.|Electronic payment interchange concentrator|

---

FR2733379B1|1995-04-20|1997-06-20|Gemplus Card Int|PROCESS FOR GENERATING ELECTRONIC SIGNATURES, ESPECIALLY FOR SMART CARDS|

---

JP3597647B2|1995-09-29|2004-12-08|株式会社東芝|Encoding method and apparatus|

---

US5783808A|1996-01-11|1998-07-21|J. D. Carreker And Associates, Inc.|Electronic check presentment system having transaction level reconciliation capability|

---

US6016484A|1996-04-26|2000-01-18|Verifone, Inc.|System, method and article of manufacture for network electronic payment instrument and certification of payment and credit collection utilizing a payment|

---

FI111674B|1996-10-31|2003-08-29|Nokia Corp|The user interface|

---

US8225089B2|1996-12-04|2012-07-17|Otomaku Properties Ltd., L.L.C.|Electronic transaction systems utilizing a PEAD and a private key|

---

US6175922B1|1996-12-04|2001-01-16|Esign, Inc.|Electronic transaction systems and methods therefor|

---

US5917913A|1996-12-04|1999-06-29|Wang; Ynjiun Paul|Portable electronic authorization devices and methods therefor|

---

US6164528A|1996-12-31|2000-12-26|Chequemark Patent, Inc.|Check writing point of sale system|

---

JPH10255112A|1997-03-12|1998-09-25|Oki Electric Ind Co Ltd|Automatic teller machine monitoring method and system therefor|

---

US6193152B1|1997-05-09|2001-02-27|Receiptcity.Com, Inc.|Modular signature and data-capture system and point of transaction payment and reward system|

---

GB9715256D0|1997-07-21|1997-09-24|Rank Xerox Ltd|Token-based docement transactions|

---

JPH1139385A|1997-07-23|1999-02-12|Oki Electric Ind Co Ltd|Method for calculating carriage sum and medium recording calculation program of carriage sum|

---

US6393462B1|1997-11-13|2002-05-21|International Business Machines Corporation|Method and apparatus for automatic downloading of URLs and internet addresses|

---

US6408087B1|1998-01-13|2002-06-18|Stmicroelectronics, Inc.|Capacitive semiconductor user input device|

---

US6504934B1|1998-01-23|2003-01-07|Onkyo Corporation|Apparatus and method for localizing sound image|

---

JP3574559B2|1998-01-27|2004-10-06|株式会社エヌ・ティ・ティ・データ|Electronic ticket system, collection terminal, service providing terminal, user terminal, electronic ticket collection method and recording medium|

---

FI980427A|1998-02-25|1999-08-26|Ericsson Telefon Ab L M|Procedure, arrangement and device for verification|

---

US6189785B1|1998-04-14|2001-02-20|International Check Services|Demand deposit account data processing system|

---

US20020002039A1|1998-06-12|2002-01-03|Safi Qureshey|Network-enabled audio device|

---

JPH1173530A|1998-07-15|1999-03-16|Yokogawa Electric Corp|Radio type fare payment system|

---

US6328207B1|1998-08-11|2001-12-11|Electronic Data Systems Corporation|Method and apparatus for automated cashing of checks|

---

WO2000016210A1|1998-09-17|2000-03-23|Nexchange Corporation|Affiliate commerce system and method|

---

JP3580710B2|1998-10-15|2004-10-27|松下電器産業株式会社|Distributed Internet Browser System and Display Method|

---

US6178403B1|1998-12-16|2001-01-23|Sharp Laboratories Of America, Inc.|Distributed voice capture and recognition system|

---

US20020059295A1|1999-01-29|2002-05-16|Harold Aaron Ludtke|Method and system for distributed queues in a multimedia network|

---

JP3921865B2|1999-03-11|2007-05-30|カシオ計算機株式会社|Data processing system and program recording medium thereof|

---

EP2367150A3|1999-04-30|2013-04-17|PayPal, Inc.|System and method for electronically exchanging value among distributed users|

---

CA2377706A1|1999-06-18|2000-12-28|Echarge Corporation|Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account|

---

US7716080B2|1999-06-23|2010-05-11|Signature Systems, Llc|Method and system for using multi-function cards for storing, managing and aggregating reward points|

---

US20030181201A1|1999-07-09|2003-09-25|Daniel S. Bomze|Mobile communication device for electronic commerce|

---

US6553345B1|1999-08-26|2003-04-22|Matsushita Electric Industrial Co., Ltd.|Universal remote control allowing natural language modality for television and multimedia searches and requests|

---

US20040169722A1|1999-10-16|2004-09-02|Pena Martin Rangel|Method and system for computer-aided telecommunication and financial transactions|

---

WO2001031788A1|1999-10-27|2001-05-03|Firooz Ghassabian|Integrated keypad system|

---

DE60032863D1|1999-11-30|2007-02-22|Citibank Na|A system and method for performing an electronic transaction using an electronic purse using a transaction proxy|

---

US6398646B1|2000-01-06|2002-06-04|Melange Computer Services, Inc.|Method and system for storing preselected numbers for use in games of bingo|

---

WO2001065446A1|2000-02-29|2001-09-07|Cdcoupon, Llc|Method and system for distribution of electronic coupons|

---

EP1133119B1|2000-03-10|2006-12-13|Nokia Corporation|Proximity based service adaption|

---

US20010039497A1|2000-03-30|2001-11-08|Hubbard Edward A.|System and method for monitizing network connected user bases utilizing distributed processing systems|

---

SG142135A1|2000-04-26|2008-05-28|Applic Co Ltd Comp|Method for managing buyer transactions and settlements using communication network between computers, and method for relaying information following buyer consumption trends to the buyer|

---

US20020046064A1|2000-05-19|2002-04-18|Hector Maury|Method and system for furnishing an on-line quote for an insurance product|

---

JP2001331758A|2000-05-22|2001-11-30|Sumisho Computer Systems Corp|Authentication work flow system, authentication server device, authentication method for liquidation, and recording medium|

---

JP4914533B2|2000-06-05|2012-04-11|株式会社三井住友銀行|Information processing apparatus and information processing method|

---

US6714233B2|2000-06-21|2004-03-30|Seiko Epson Corporation|Mobile video telephone system|

---

SE517484C2|2000-06-30|2002-06-11|Nokia Corp|Parental control of devices that deliver media content|

---

US7081905B1|2000-06-30|2006-07-25|International Business Machines Corporation|Method and apparatus for dynamically controlling scroller speed employed for a user interface of a wearable appliance|

---

EP1356438B1|2000-07-10|2014-06-18|PayPal, Inc.|System and method for verifying a financial instrument|

---

US7529563B1|2000-07-10|2009-05-05|Pitroda Satyan G|System for distribution and use of virtual stored value cards|

---

US7359880B2|2000-07-11|2008-04-15|Abel Luther C|System and method for consumer control over card-based transactions|

---

US7450969B1|2000-08-28|2008-11-11|Wideray, Inc.|Two radio interface for mobile communication device for electronic commerce|

---

US20020029169A1|2000-09-05|2002-03-07|Katsuhiko Oki|Method and system for e-transaction|

---

JP2002099854A|2000-09-21|2002-04-05|Sanyo Electric Co Ltd|Card settlement member store terminal, card settlement service system and card effectiveness judging method in card settlement|

---

AU9285701A|2000-09-21|2002-04-02|American Calcar Inc|Technique for operating a vehicle effectively and safely|

---

US7337144B1|2000-09-28|2008-02-26|Microsoft Corporation|Method and system for restricting the usage of payment accounts|

---

US7155411B1|2000-09-28|2006-12-26|Microsoft Corporation|Integrating payment accounts and an electronic wallet|

---

US20040143553A1|2000-12-01|2004-07-22|Torget John W.|System and method for remotely generating instruments|

---

US7080159B2|2000-12-15|2006-07-18|Ntt Docomo, Inc.|Method and system for effecting migration of application among heterogeneous devices|

---

US8949902B1|2001-02-06|2015-02-03|Rovi Guides, Inc.|Systems and methods for providing audio-based guidance|

---

US20020116276A1|2001-02-20|2002-08-22|Ottley Steven R.|Intuitive graphical user interface for dynamically addressing electronic shopping cart deliverables|

---

JP2002288125A|2001-03-27|2002-10-04|Just Syst Corp|System and method for reproducing working state|

---

US20020142734A1|2001-04-03|2002-10-03|James Wickstead|Miniaturized wrist phone|

---

US7079652B1|2001-05-01|2006-07-18|Harris Scott C|Login renewal based on device surroundings|

---

JP2002342356A|2001-05-18|2002-11-29|Nec Software Kyushu Ltd|System, method and program for providing information|

---

JP2002351768A|2001-05-29|2002-12-06|Mitsubishi Electric Corp|Transferor terminal and information transfer method|

---

JP2003016398A|2001-06-27|2003-01-17|Sony Corp|Portable terminal machine|

---

US7305350B1|2001-06-29|2007-12-04|Aol Llc|System for notifying an online client of a mobile vendor|

---

US7200590B2|2001-08-15|2007-04-03|Yahoo! Inc.|Data sharing|

---

US6922147B1|2001-07-12|2005-07-26|Ann S. Viksnins|Warning system sensing child left behind in infant seat in vehicle|

---

JP2003030245A|2001-07-12|2003-01-31|Sony Corp|Device, system, method and program for reading information, server device, terminal device, method and program for providing information and recording medium|

---

AU2002327322A1|2001-07-24|2003-02-17|First Usa Bank, N.A.|Multiple account card and transaction routing|

---

CN1284088C|2001-08-03|2006-11-08|松下电器产业株式会社|Access control system|

---

US7099845B2|2001-08-16|2006-08-29|Ncr Corporation|Electronic check presentment with image interchange system and method of operating an electronic check presentment with image interchange system|

---

US8050997B1|2001-08-23|2011-11-01|Paypal Inc.|Instant availability of electronically transferred funds|

---

US20030188183A1|2001-08-27|2003-10-02|Lee Lane W.|Unlocking method and system for data on media|

---

US7191233B2|2001-09-17|2007-03-13|Telecommunication Systems, Inc.|System for automated, mid-session, user-directed, device-to-device session transfer system|

---

US7099850B1|2001-09-21|2006-08-29|Jpmorgan Chase Bank, N.A.|Methods for providing cardless payment|

---

AUPR815201A0|2001-10-08|2001-11-01|University Of Wollongong, The|Session mobility using digital items|

---

US20040248548A1|2001-10-31|2004-12-09|Takanori Niwa|Portable terminal and pos terminal|

---

JP3974375B2|2001-10-31|2007-09-12|株式会社東芝|Person recognition device, person recognition method, and traffic control device|

---

US7415502B2|2001-11-16|2008-08-19|Sbc Technology Resources, Inc.|Method and system for intelligent routing based on presence detection|

---

US7831930B2|2001-11-20|2010-11-09|Universal Electronics Inc.|System and method for displaying a user interface for a remote control application|

---

US6644546B2|2002-01-02|2003-11-11|International Business Machines Corporation|System and method for electronic check conversion at a point-of-sale terminal|

---

US6970855B2|2002-01-29|2005-11-29|Pitney Bowes Inc.|Method and system for enterprise-level unassisted customer shipping|

---

US7095442B2|2002-01-31|2006-08-22|Hewlett-Packard Development Company, L.P.|Method and apparatus for capturing an image|

---

US7904360B2|2002-02-04|2011-03-08|Alexander William EVANS|System and method for verification, authentication, and notification of a transaction|

---

EP1490846A2|2002-04-03|2004-12-29|Swivel Secure Limited|System and method for secure credit and debit card transactions|

---

US6971017B2|2002-04-16|2005-11-29|Xerox Corporation|Ad hoc secure access to documents and services|

---

US7707120B2|2002-04-17|2010-04-27|Visa International Service Association|Mobile account authentication service|

---

AU2003239385A1|2002-05-10|2003-11-11|Richard R. Reisman|Method and apparatus for browsing using multiple coordinated device|

---

JP2003346059A|2002-05-24|2003-12-05|Nec Engineering Ltd|On-line shopping system|

---

CA2430403C|2002-06-07|2011-06-21|Hiroyuki Hashimoto|Sound image control system|

---

US7356516B2|2002-06-13|2008-04-08|Visa U.S.A. Inc.|Method and system for facilitating electronic dispute resolution|

---

US20030236746A1|2002-06-19|2003-12-25|Turner Michael B.|Check and cash dispensing machine and method|

---

US7822688B2|2002-08-08|2010-10-26|Fujitsu Limited|Wireless wallet|

---

US7606560B2|2002-08-08|2009-10-20|Fujitsu Limited|Authentication services using mobile device|

---

US7494055B2|2002-09-17|2009-02-24|Vivotech, Inc.|Collaborative negotiation techniques for mobile personal trusted device financial transactions|

---

US20040073432A1|2002-10-15|2004-04-15|Stone Christopher J.|Webpad for the disabled|

---

AU2003296927A1|2002-11-05|2004-06-07|Todd Silverstein|Remote purchasing system and method|

---

KR100477150B1|2002-12-06|2005-03-17|에스케이 텔레콤주식회사|Release Management System and Method for Locking Function of Mobile Communication Terminal with Electronic Wallet|

---

KR100403196B1|2002-12-11|2003-10-30|Hasung Data System Co Ltd|Settling system using mobile communication terminal, method therefor, and recording medium storing program for the setting system|

---

US20040122685A1|2002-12-20|2004-06-24|Daryl Bunce|Verification system for facilitating transactions via communication networks, and associated method|

---

JP4293516B2|2003-02-20|2009-07-08|株式会社三菱東京Ｕｆｊ銀行|Account transfer application reception system, method and program|

---

US7373657B2|2003-03-10|2008-05-13|Avaya Technology Corp.|Method and apparatus for controlling data and software access|

---

JP4812234B2|2003-03-19|2011-11-09|ソニー株式会社|Payment management device, portable information terminal, and program|

---

US7369759B2|2003-03-27|2008-05-06|Matsushita Electric Industrial Co., Ltd.|Eye image pickup apparatus, iris authentication apparatus and portable terminal device having iris authentication function|

---

JP4340566B2|2003-04-01|2009-10-07|株式会社リコー|Web page generation apparatus, embedded apparatus, Web page generation control method, Web page generation program, and recording medium|

---

WO2004095414A1|2003-04-18|2004-11-04|Keyless Systems Ltd|Systems to enhance data entry in mobile and fixed environment|

---

US7644019B2|2003-04-21|2010-01-05|Buysafe, Inc.|Safe transaction guaranty|

---

JP2004356816A|2003-05-28|2004-12-16|Hitachi Ltd|Communication system, communication terminal, and operating program for communication terminal|

---

MXPA05013288A|2003-06-16|2007-04-18|Uru Technology Inc|Method and system for creating and operating biometrically enabled multi-purpose credential management devices.|

---

WO2005003907A2|2003-06-26|2005-01-13|Ebay Inc.|Method and apparatus to authenticate and authorize user access to a system|

---

KR100538579B1|2003-07-14|2005-12-22|이지케어텍|Method For Management Of Medical Affairs Form In On-line|

---

US7761513B2|2003-07-14|2010-07-20|Sony Corporation|Information recording device, information recording method, and information recording program|

---

US8234395B2|2003-07-28|2012-07-31|Sonos, Inc.|System and method for synchronizing operations among a plurality of independently clocked digital data processing devices|

---

US7571014B1|2004-04-01|2009-08-04|Sonos, Inc.|Method and apparatus for controlling multimedia players in a multi-zone system|

---

US7082573B2|2003-07-30|2006-07-25|America Online, Inc.|Method and system for managing digital assets|

---

AU2003257366A1|2003-08-08|2005-02-25|Paycool, International, Ltd.|Methods for facilitating validation of financial transactions made through a wireless communication network|

---

US7546470B2|2003-08-13|2009-06-09|International Business Machines Corporation|Selective computer component activation apparatus method and system|

---

CN1525723A|2003-09-16|2004-09-01|海信集团有限公司|Method for receiving and transmitting handset short message by computer|

---

US7756726B2|2003-09-25|2010-07-13|International Business Machines Corporation|Secured medical sign-in|

---

US7532196B2|2003-10-30|2009-05-12|Microsoft Corporation|Distributed sensing techniques for mobile devices|

---

US7415720B2|2003-10-31|2008-08-19|Samsung Electronics Co., Ltd.|User authentication system and method for controlling the same|

---

US8078481B2|2003-12-05|2011-12-13|John Steinbarth|Benefits administration system and methods of use and doing business|

---

US7835971B2|2003-12-12|2010-11-16|Michael Stockton|Method and system configured for facilitating management of international trade receivables transactions|

---

JP2005292542A|2004-04-01|2005-10-20|Matsushita Electric Ind Co Ltd|Eye imaging apparatus and mobil terminal device|

---

US8290603B1|2004-06-05|2012-10-16|Sonos, Inc.|User interfaces for controlling and manipulating groupings in a multi-zone media system|

---

US20180053157A1|2010-01-08|2018-02-22|Blackhawk Network, Inc.|Systems and methods for consumer modifiable payment card transactions|

---

WO2005109829A1|2004-05-06|2005-11-17|Koninklijke Philips Electronics N.V.|Method device and program for seamlessly transferring the execution of a software application from a first to a second device|

---

US20050250538A1|2004-05-07|2005-11-10|July Systems, Inc.|Method and system for making card-based payments using mobile devices|

---

US7370244B2|2004-05-26|2008-05-06|Sap Ag|User-guided error correction|

---

US20060021003A1|2004-06-23|2006-01-26|Janus Software, Inc|Biometric authentication system|

---

JP4281638B2|2004-07-13|2009-06-17|ソニー株式会社|Information processing system, information processing apparatus, information processing method, and information recording medium|

---

US7870071B2|2004-09-08|2011-01-11|American Express Travel Related Services Company, Inc.|Systems, methods, and devices for combined credit card and stored value transaction accounts|

---

JP4699139B2|2004-09-14|2011-06-08|富士フイルム株式会社|Security system|

---

JP2006093912A|2004-09-22|2006-04-06|Casio Hitachi Mobile Communications Co Ltd|Mobile phone device and program|

---

US20100205091A1|2004-10-22|2010-08-12|Zevez Payments, Inc.|Automated payment transaction system|

---

US8478363B2|2004-11-22|2013-07-02|The Invention Science Fund I, Llc|Transfer then sleep|

---

JP2006163960A|2004-12-09|2006-06-22|Sharp Corp|Portable communication terminal with settlement function, billing and settlement system and authentication method in billing and settlement|

---

US7629966B2|2004-12-21|2009-12-08|Microsoft Corporation|Hard tap|

---

JP2006197071A|2005-01-12|2006-07-27|Konica Minolta Photo Imaging Inc|Method of controlling radio communication system, radio communication system, radio terminal device, image data communication system, and program|

---

US20060161621A1|2005-01-15|2006-07-20|Outland Research, Llc|System, method and computer program product for collaboration and synchronization of media content on a plurality of media players|

---

US20060208060A1|2005-01-18|2006-09-21|Isaac Mendelovich|Method for managing consumer accounts and transactions|

---

US8700729B2|2005-01-21|2014-04-15|Robin Dua|Method and apparatus for managing credentials through a wireless network|

---

US7197324B2|2005-01-31|2007-03-27|Sweeney Robert J|Permission based text messaging|

---

US20060179404A1|2005-02-08|2006-08-10|Microsoft Corporation|Method for a browser auto form fill|

---

US7707044B2|2005-02-11|2010-04-27|Avaya Inc.|Use of location awareness to transfer communications sessions between terminals in a healthcare environment|

---

ES2662254T3|2005-03-07|2018-04-05|Nokia Technologies Oy|Method and mobile terminal device that includes smart card module and near field communications media|

---

KR20060102724A|2005-03-24|2006-09-28|삼성전자주식회사|Mobile terminal and remote control device thereof|

---

JP2006277670A|2005-03-30|2006-10-12|Nec Corp|Settlement means selection method, settlement means selection system, and computer program|

---

US20060224882A1|2005-03-31|2006-10-05|Microsoft Corporation|Method and system for unlocking a computing device|

---

JP2006303701A|2005-04-18|2006-11-02|Fujitsu Ltd|Electronic equipment, and method and program of controlling operation suppression thereof|

---

EP1872188A4|2005-04-19|2011-04-27|Microsoft Corp|Network commercial transactions|

---

US7793851B2|2005-05-09|2010-09-14|Dynamics Inc.|Dynamic credit card with magnetic stripe and embedded encoder and methods for using the same to provide a copy-proof credit card|

---

US8244179B2|2005-05-12|2012-08-14|Robin Dua|Wireless inter-device data processing configured through inter-device transmitted data|

---

CN100440947C|2005-05-13|2008-12-03|海尔集团公司|Multifunctional television|

---

US9743266B2|2005-05-23|2017-08-22|Invention Science Fund I, Llc|Device pairing via device to device contact|

---

US20060288226A1|2005-06-15|2006-12-21|Stelor Productions, Llc.|System and method for establishing and authorizing a security code|

---

US8452654B1|2005-06-16|2013-05-28|Rbs Nb|System and method for issuing rewards to card holders|

---

US10567376B2|2012-08-24|2020-02-18|Sensible Vision, Inc.|System and method for providing secure access to an electronic device using multifactor authentication|

---

NO324406B1|2005-06-20|2007-10-08|Telenor Asa|SIM RFID reader with WLAN access|

---

AU2006264204A1|2005-06-27|2007-01-04|Embed International Pty Ltd|A light signalling system|

---

US7831520B2|2005-06-28|2010-11-09|Ebay Inc.|Mobile device communication system|

---

US8811392B1|2005-07-12|2014-08-19|Brixham Solutions Ltd.|Lightweight control-plane signaling for aggregation devices in a network|

---

US20070013662A1|2005-07-13|2007-01-18|Fauth Richard M|Multi-configurable tactile touch-screen keyboard and associated methods|

---

US7567898B2|2005-07-26|2009-07-28|Broadcom Corporation|Regulation of volume of voice in conjunction with background sound|

---

JP4663441B2|2005-07-26|2011-04-06|株式会社エヌ・ティ・ティ・ドコモ|Mobile terminal device and electronic payment system|

---

CN1908981A|2005-08-01|2007-02-07|富士通株式会社|Wireless computer wallet for physical point of sale transactions|

---

JP2007041976A|2005-08-05|2007-02-15|Canon Inc|Data processing apparatus, file processing method, storage medium and program|

---

EP1760619A1|2005-08-19|2007-03-07|STMicroelectronics Ltd.|System for restricting data access|

---

EP2017729B1|2005-08-23|2018-08-08|BlackBerry Limited|Method and system fortransferring an application state from a first electronic device to a second electronic device|

---

WO2007041834A1|2005-10-07|2007-04-19|Memory Experts International Inc.|Method and apparatus for secure credential entry without physical entry|

---

US8515348B2|2005-10-28|2013-08-20|Electro Industries/Gauge Tech|Bluetooth-enable intelligent electronic device|

---

US7849323B2|2005-11-09|2010-12-07|Emc Corporation|Password presentation for multimedia devices|

---

US20070115933A1|2005-11-22|2007-05-24|Sbc Knowledge Ventures Lp|Method for maintaining continuity of a multimedia session between media devices|

---

US20070131759A1|2005-12-14|2007-06-14|Cox Mark A|Smartcard and magnetic stripe emulator with biometric authentication|

---

US20070150918A1|2005-12-22|2007-06-28|Sony Ericsson Mobile Communications Ab|Methods, devices, and computer program products for providing parental control over access to media content using a mobile terminal|

---

US7657849B2|2005-12-23|2010-02-02|Apple Inc.|Unlocking a device by performing gestures on an unlock image|

---

JP4881615B2|2005-12-23|2012-02-22|パナソニック株式会社|Identification management system for authentication of electronic devices|

---

US7509588B2|2005-12-30|2009-03-24|Apple Inc.|Portable electronic device with interface reconfiguration mode|

---

US8112787B2|2005-12-31|2012-02-07|Broadcom Corporation|System and method for securing a credential via user and server verification|

---

CN101268470B|2006-01-10|2012-01-11|富士通株式会社|Portable terminal device, address book transmitter, information displaying method in portable terminal device, address book transmitting method|

---

AT399428T|2006-01-10|2008-07-15|Alcatel Lucent|PROCEDURE AND ACCESS SERVER TO PROVIDE A USER A CENTRAL REGISTRATION PROCEDURE|

---

AU2007257435A1|2006-01-20|2007-12-13|Conversational Computing Corporation|Wearable display interface client|

---

US9118656B2|2006-01-26|2015-08-25|Imprivata, Inc.|Systems and methods for multi-factor authentication|

---

US8078990B2|2006-02-01|2011-12-13|Research In Motion Limited|Secure device sharing|

---

AT510396T|2006-02-01|2011-06-15|Research In Motion Ltd|SYSTEM AND METHOD FOR VALIDATING A USER ACCOUNT WITH A WIRELESS DEVICE|

---

EP1987627B1|2006-02-03|2016-11-16|Mideye AB|A system, an arrangement and a method for end user authentication|

---

US7353991B2|2006-02-21|2008-04-08|David Benjamin Esplin|System and method for managing wireless point-of-sale transactions|

---

US9830634B2|2006-02-23|2017-11-28|International Business Machines Corporation|Performing secure financial transactions in an instant messaging environment|

---

WO2007102110A2|2006-03-07|2007-09-13|Koninklijke Philips Electronics N.V.|Method of transferring data|

---

JP4850682B2|2006-03-07|2012-01-11|富士通株式会社|Lock system, lock release device, device, lock release method and circuit device|

---

US9953097B2|2006-03-16|2018-04-24|Ebay Inc.|System and method for managing network traffic routing|

---

WO2007107708A2|2006-03-20|2007-09-27|British Telecommunications Public Limited Company|Establishing communications|

---

US20070226778A1|2006-03-22|2007-09-27|Jorg Pietruszka|Bluetooth theft protection|

---

WO2007116521A1|2006-04-10|2007-10-18|Panasonic Corporation|Portable terminal and credit card selection method using the same|

---

EP2013848A4|2006-04-17|2011-07-06|Veritec Inc|Methods and systems for secure transactions with electronic devices|

---

US7907896B2|2006-04-28|2011-03-15|Motorola Mobility, Inc.|Mobile commerce method and device|

---

US8396711B2|2006-05-01|2013-03-12|Microsoft Corporation|Voice authentication system and method|

---

US20070260547A1|2006-05-05|2007-11-08|On Q Technologies Pty Ltd.|System and Method for Purchasing Digital Content|

---

EP2018744B1|2006-05-05|2010-09-08|Nxp B.V.|Authentication of devices in a wireless network|

---

JP2007304854A|2006-05-11|2007-11-22|Hitachi Electronics Service Co Ltd|Security system and personal computer for maintenance|

---

US8086698B2|2006-06-02|2011-12-27|Google Inc.|Synchronizing configuration information among multiple clients|

---

JP4903501B2|2006-06-15|2012-03-28|Ｎｅｃカシオモバイルコミュニケーションズ株式会社|Portable terminal device with authentication function and program|

---

US8594742B2|2006-06-21|2013-11-26|Symbol Technologies, Inc.|System and method for monitoring a mobile device|

---

US8467766B2|2006-07-06|2013-06-18|Qualcomm Incorporated|Methods and systems for managing payment sources in a mobile environment|

---

US9911114B2|2006-07-06|2018-03-06|Qualcomm Incorporated|Methods and systems for making a payment via a stored value card in a mobile environment|

---

US20080010387A1|2006-07-07|2008-01-10|Bryce Allen Curtis|Method for defining a Wiki page layout using a Wiki page|

---

US8079068B2|2006-07-17|2011-12-13|Research In Motion Limited|Management of multiple connections to a security token access device|

---

US8112794B2|2006-07-17|2012-02-07|Research In Motion Limited|Management of multiple connections to a security token access device|

---

US20080011827A1|2006-07-17|2008-01-17|Research In Motion Limited|Automatic management of security information for a security token access device with multiple connections|

---

KR101305497B1|2006-08-14|2013-09-05|삼성전자주식회사|Client Computer, Remote Control System And Remote Control Method|

---

US9773262B2|2006-08-17|2017-09-26|Mastercard International Incorporated Purchase|Integrated file structure useful in connection with apparatus and method for facilitating account restructuring in an electronic bill payment system|

---

US7886962B2|2006-08-17|2011-02-15|Verizon Patent And Licensing Inc.|Multi-function transaction device|

---

US20080052181A1|2006-08-23|2008-02-28|Taram Devitt-Carolan|Integrated system for providing user services|

---

WO2008025058A1|2006-08-27|2008-03-06|My Mobile Watch Limited|Gsm mobile watch phone|

---

CN100591011C|2006-08-31|2010-02-17|华为技术有限公司|Identification method and system|

---

US8106856B2|2006-09-06|2012-01-31|Apple Inc.|Portable electronic device for photo management|

---

JP4963388B2|2006-09-12|2012-06-27|日立オムロンターミナルソリューションズ株式会社|Biometric authentication device and operation guidance notification method|

---

US9202509B2|2006-09-12|2015-12-01|Sonos, Inc.|Controlling and grouping in a multi-zone media system|

---

US8452978B2|2006-09-15|2013-05-28|Identity Metrics, LLC|System and method for user authentication and dynamic usability of touch-screen devices|

---

US20080208681A1|2006-09-28|2008-08-28|Ayman Hammad|Payment using a mobile device|

---

US7983614B2|2006-09-29|2011-07-19|Sony Ericsson Mobile Communications Ab|Handover for audio and video playback devices|

---

US20130212655A1|2006-10-02|2013-08-15|Hector T. Hoyos|Efficient prevention fraud|

---

US8434133B2|2006-10-06|2013-04-30|Fmr Llc|Single-party, secure multi-channel authentication|

---

GB0621189D0|2006-10-25|2006-12-06|Payfont Ltd|Secure authentication and payment system|

---

US20080114678A1|2006-11-15|2008-05-15|David Lawrence Bennett|Method and apparatus for remote authorization|

---

JP2010509992A|2006-11-17|2010-04-02|任天堂株式会社|Video game program download system and download method|

---

CN101730907A|2006-11-22|2010-06-09|马克·A·库克斯|Point0f sale transaction device with magnetic stripe emulator and biometric authentication|

---

US20080120707A1|2006-11-22|2008-05-22|Alexander Ramia|Systems and methods for authenticating a device by a centralized data server|

---

GB0624582D0|2006-12-08|2007-01-17|Visible Computing Ltd|USB autorun devices|

---

US8583090B2|2006-12-29|2013-11-12|Nokia Corporation|Transferring task completion to another device|

---

KR20080064395A|2007-01-05|2008-07-09|삼성전자주식회사|Method for searching information in mobile communication terminal using card settlement information|

---

US8707400B2|2007-01-22|2014-04-22|Apple Inc.|System and method for implementing an extended authentication and authorization credential store|

---

CN101232631B|2007-01-23|2011-08-31|阿里巴巴集团控股有限公司|System and method for communication terminal to perform safety authentication through short messages|

---

US8793184B2|2007-02-12|2014-07-29|Visa U.S.A. Inc.|Mobile payment services|

---

US20080208762A1|2007-02-22|2008-08-28|First Data Corporation|Payments using a mobile commerce device|

---

WO2008104995A2|2007-02-28|2008-09-04|Raja Raman|A method and system for close range communication using audio tones|

---

US8362873B2|2007-03-01|2013-01-29|Deadman Technologies, Llc|Control of equipment using remote display|

---

DE602007007581D1|2007-04-17|2010-08-19|Harman Becker Automotive Sys|Acoustic localization of a speaker|

---

US8364139B2|2007-04-19|2013-01-29|Apple Inc.|Personal area network systems and devices and methods for use thereof|

---

CN101299694B|2007-04-30|2012-04-25|华为技术有限公司|Method and system for managing caller in household network, household gateway|

---

US8325936B2|2007-05-04|2012-12-04|Bose Corporation|Directionally radiating sound in a vehicle|

---

US8483413B2|2007-05-04|2013-07-09|Bose Corporation|System and method for directionally radiating sound|

---

US8606512B1|2007-05-10|2013-12-10|Allstate Insurance Company|Route risk mitigation|

---

US7979809B2|2007-05-11|2011-07-12|Microsoft Corporation|Gestured movement of object to display edge|

---

US8705722B2|2007-05-22|2014-04-22|Verizon Patent And Licensing Inc.|Automatic routing of communications to user endpoints|

---

GB2460306B|2008-05-29|2013-02-13|Intrasonics Sarl|Data embedding system|

---

CN101321156B|2007-06-06|2011-05-04|艾威梯科技有限公司|Method and system for second intercommunication protocol expansion based on first intercommunication protocol|

---

US20080313257A1|2007-06-15|2008-12-18|Allen James D|Method and Apparatus for Policy-Based Transfer of an Application Environment|

---

JP5110983B2|2007-06-29|2012-12-26|日立オムロンターミナルソリューションズ株式会社|Biometric authentication processing system|

---

US7930249B2|2007-07-11|2011-04-19|Qualcomm Incorporated|Mobile wireless financial instrument for automatically selecting a payment instrument|

---

EP2018032A1|2007-07-20|2009-01-21|Nederlandse Organisatie voor toegepast- natuurwetenschappelijk onderzoek TNO|Identification of proximate mobile devices|

---

US8660893B2|2007-07-23|2014-02-25|Visa U.S.A. Inc.|Multi-vendor multi-loyalty currency program|

---

US8316410B2|2007-07-23|2012-11-20|At&T Intellectual Property I, Lp|Apparatus and method for communicating media between communication devices|

---

US20090037326A1|2007-07-30|2009-02-05|Sriram Chitti|Virtual Card Selector for a Portable Electronic Device|

---

WO2009038826A2|2007-07-31|2009-03-26|International Business Machines Corporation|Biometric authentication device, system and method of biometric authentication|

---

JP5104124B2|2007-08-22|2012-12-19|日本電気株式会社|Mobile terminal and method of restricting use thereof|

---

US20090057396A1|2007-08-27|2009-03-05|Eric Barbour|Method and system for multiple account, token-based single transactions|

---

US8532285B2|2007-09-05|2013-09-10|Avaya Inc.|Method and apparatus for call control using motion and position information|

---

US9165175B2|2007-09-07|2015-10-20|Apple Inc.|Finger sensing apparatus performing secure software update and associated methods|

---

EP2203865A2|2007-09-24|2010-07-07|Apple Inc.|Embedded authentication systems in an electronic device|

---

US8893284B2|2007-10-03|2014-11-18|Motorola Mobility Llc|Method and system for providing extended authentication|

---

US9536256B2|2007-10-08|2017-01-03|First Data Corporation|Systems and methods for stored-value exchange within social networking environments|

---

US20090100383A1|2007-10-16|2009-04-16|Microsoft Corporation|Predictive gesturing in graphical user interface|

---

JP5267966B2|2007-10-19|2013-08-21|Ｎｅｃカシオモバイルコミュニケーションズ株式会社|Portable terminal device and portable terminal processing program|

---

EP2056627A1|2007-10-30|2009-05-06|SonicEmotion AG|Method and device for improved sound field rendering accuracy within a preferred listening area|

---

US8818941B2|2007-11-11|2014-08-26|Microsoft Corporation|Arrangement for synchronizing media files with portable devices|

---

US8154608B2|2007-11-13|2012-04-10|Olympus Corporation|Digital camera security|

---

TW200929974A|2007-11-19|2009-07-01|Ibm|System and method for performing electronic transactions|

---

US7689508B2|2007-11-20|2010-03-30|Wells Fargo Bank N.A.|Mobile device credit account|

---

EP2063327A1|2007-11-26|2009-05-27|EM Microelectronic-Marin SA|Electronic circuit for managing the operation of peripheral devices of a watch|

---

US8624809B2|2007-11-29|2014-01-07|Apple Inc.|Communication using light-emitting device|

---

US8352323B2|2007-11-30|2013-01-08|Blaze Mobile, Inc.|Conducting an online payment transaction using an NFC enabled mobile communication device|

---

US7873748B2|2007-11-30|2011-01-18|International Business Machines Corporation|Synchronization of locally and remotely stored browser data|

---

US8849914B2|2007-12-20|2014-09-30|The Vanguard Group, Inc.|System and method for synchronized co-browsing by users in different web sessions|

---

US20090159704A1|2007-12-24|2009-06-25|Dynamics Inc.|Cards and devices with magnetic emulators and magnetic read-head detectors|

---

TWI359381B|2007-12-25|2012-03-01|Htc Corp|Method for unlocking a locked computing device and|

---

US7802720B2|2008-01-04|2010-09-28|Intuit Inc.|Method and system for performing a card-present transaction using image capture on a portable device|

---

WO2009086599A1|2008-01-07|2009-07-16|Avega Systems Pty Ltd|A user interface for managing the operation of networked media playback devices|

---

US8724600B2|2008-01-07|2014-05-13|Tymphany Hong Kong Limited|Systems and methods for providing a media playback in a networked environment|

---

US20090182674A1|2008-01-14|2009-07-16|Amol Patel|Facilitating financial transactions with a network device|

---

US8424079B2|2008-01-25|2013-04-16|Research In Motion Limited|Method, system and mobile device employing enhanced user authentication|

---

TWI355111B|2008-01-31|2011-12-21|Yfy Rfid Technologies Company Ltd|Antenna system and antenna thereof|

---

US8344998B2|2008-02-01|2013-01-01|Wimm Labs, Inc.|Gesture-based power management of a wearable portable electronic device with display|

---

JP2009187146A|2008-02-04|2009-08-20|Fuji Xerox Co Ltd|Information processing system and information processing program|

---

US9947002B2|2008-02-15|2018-04-17|First Data Corporation|Secure authorization of contactless transaction|

---

US8996867B2|2008-02-28|2015-03-31|At&T Intellectual Property I, L.P.|Method and device for end-user verification of an electronic transaction|

---

US8595757B2|2008-03-05|2013-11-26|At&T Intellectual Property I, L.P.|System and method of sharing media content|

---

US20090248737A1|2008-03-27|2009-10-01|Microsoft Corporation|Computing environment representation|

---

JP4692566B2|2008-03-28|2011-06-01|ブラザー工業株式会社|Communication device|

---

US8077157B2|2008-03-31|2011-12-13|Intel Corporation|Device, system, and method of wireless transfer of files|

---

JP5261009B2|2008-04-16|2013-08-14|パナソニック株式会社|Face image registration device|

---

US8051370B2|2008-04-23|2011-11-01|Microsoft Corporation|Intelligent autocompletion|

---

US7860936B1|2008-05-09|2010-12-28|Symantec Corporation|Verifying instant messaging aliases via online parental control accounts|

---

US20090282078A1|2008-05-12|2009-11-12|Motion Limited|Unified media file architecture|

---

US9024890B2|2008-05-17|2015-05-05|David H. Chin|Comparison of an applied gesture on a touch screen of a mobile device with a remotely stored security gesture|

---

EP2294539A1|2008-05-18|2011-03-16|Google Inc.|Secured electronic transaction system|

---

US20140025520A1|2008-06-06|2014-01-23|Ebay Inc.|Biometric authentication of mobile financial transactions by trusted service managers|

---

US20090307140A1|2008-06-06|2009-12-10|Upendra Mardikar|Mobile device over-the-air registration and point-of-sale payment|

---

US20090304205A1|2008-06-10|2009-12-10|Sony Corporation Of Japan|Techniques for personalizing audio levels|

---

CN102067157A|2008-06-13|2011-05-18|S·什里瓦斯塔瓦|Real time authentication of payment cards|

---

US20090311993A1|2008-06-16|2009-12-17|Horodezky Samuel Jacob|Method for indicating an active voice call using animation|

---

US8909940B2|2008-06-23|2014-12-09|Intel Corporation|Extensible pre-boot authentication|

---

KR101524616B1|2008-07-07|2015-06-02|엘지전자 주식회사|Controlling a Mobile Terminal with a Gyro-Sensor|

---

US9269010B2|2008-07-14|2016-02-23|Jumio Inc.|Mobile phone payment system using integrated camera credit card reader|

---

US8662401B2|2008-07-25|2014-03-04|First Data Corporation|Mobile payment adoption by adding a dedicated payment button to mobile device form factors|

---

US8482381B2|2008-07-31|2013-07-09|Palm, Inc.|Multi-purpose detector-based input feature for a computing device|

---

JP4748257B2|2008-08-04|2011-08-17|ソニー株式会社|Biometric authentication device|

---

US20100042517A1|2008-08-12|2010-02-18|The Westem Union Company|Universal loyalty systems and methods|

---

CA2774713A1|2009-08-14|2011-02-17|Payfone, Inc.|System and method for paying a merchant using a cellular telephone account|

---

US8127999B2|2008-08-14|2012-03-06|Visa U.S.A. Inc.|Wireless mobile communicator for contactless payment on account read from removable card|

---

US20100042835A1|2008-08-18|2010-02-18|Keep Security Inc.|System and method for permission confirmation by transmitting a secure request through a central server to a mobile biometric device|

---

US20100063926A1|2008-09-09|2010-03-11|Damon Charles Hougland|Payment application framework|

---

US8977567B2|2008-09-22|2015-03-10|Visa International Service Association|Recordation of electronic payment transaction information|

---

US20100078471A1|2008-09-30|2010-04-01|Apple Inc.|System and method for processing peer-to-peer financial transactions|

---

KR20110056561A|2008-09-30|2011-05-30|애플 인크.|Peer-to-peer financial transaction devices and methods|

---

US20100082445A1|2008-09-30|2010-04-01|Apple Inc.|Smart menu options|

---

US10380573B2|2008-09-30|2019-08-13|Apple Inc.|Peer-to-peer financial transaction devices and methods|

---

US20100082485A1|2008-09-30|2010-04-01|Apple Inc.|Portable point of purchase devices and methods|

---

US20100078472A1|2008-09-30|2010-04-01|Apple Inc.|Group peer-to-peer financial transactions|

---

US8624836B1|2008-10-24|2014-01-07|Google Inc.|Gesture-based small device input|

---

US8949955B2|2008-10-29|2015-02-03|Symantec Corporation|Method and apparatus for mobile time-based UI for VIP|

---

US20100114731A1|2008-10-30|2010-05-06|Kingston Tamara S|ELECTRONIC WALLET |

---

CN101409743A|2008-11-06|2009-04-15|中兴通讯股份有限公司|Mobile communication terminal and method for wireless communication with computer|

---

US20100125495A1|2008-11-17|2010-05-20|Smith Steven M|System and method of providing a mobile wallet at a mobile telephone|

---

US20120101881A1|2008-11-25|2012-04-26|Mary Theresa Taylor|Loyalty promotion apparatuses, methods and systems|

---

US20100131300A1|2008-11-26|2010-05-27|Fred Collopy|Visible insurance|

---

GB2466038A|2008-12-09|2010-06-16|Alexzandre Anthony Capurro|Authorisation of cashless payment using SMS|

---

US20100153265A1|2008-12-15|2010-06-17|Ebay Inc.|Single page on-line check-out|

---

WO2010077960A2|2008-12-16|2010-07-08|Deeda, Inc.|Systems and methods for purchasing, sending, and receiving gifts and donations through social networks, and other online mediums across the web, desktop, and mobile environments|

---

US8494908B2|2008-12-18|2013-07-23|Ncr Corporation|Retail checkout system and method|

---

US8331992B2|2008-12-19|2012-12-11|Verizon Patent And Licensing Inc.|Interactive locked state mobile communication device|

---

JP5084712B2|2008-12-24|2012-11-28|日立オムロンターミナルソリューションズ株式会社|User authentication terminal, authentication system, user authentication method, and user authentication program|

---

CN101770299B|2008-12-26|2013-11-06|深圳富泰宏精密工业有限公司|System and method for realizing functions of navigation keys|

---

US8505078B2|2008-12-28|2013-08-06|Qualcomm Incorporated|Apparatus and methods for providing authorized device access|

---

KR101467796B1|2009-01-12|2014-12-10|엘지전자 주식회사|Mobile terminal and method for controlling the same|

---

US20100191570A1|2009-01-23|2010-07-29|Joe Phillip Michaud|Loyalty reward program simulators|

---

US8363866B2|2009-01-30|2013-01-29|Panasonic Automotive Systems Company Of America|Audio menu navigation method|

---

US8548426B2|2009-02-20|2013-10-01|Boku, Inc.|Systems and methods to approve electronic payments|

---

US20100223542A1|2009-02-27|2010-09-02|Research In Motion Limited|Method, system and apparatus for providing pinned bookmarks|

---

US8606638B2|2009-03-02|2013-12-10|First Data Corporation|Systems, methods and apparatus for facilitating transactions using a mobile device|

---

KR101549556B1|2009-03-06|2015-09-03|엘지전자 주식회사|Mobile terminal and control method thereof|

---

JP5223736B2|2009-03-11|2013-06-26|パナソニック株式会社|Information reader|

---

JP2010211579A|2009-03-11|2010-09-24|Hitachi Omron Terminal Solutions Corp|Biometric authentication apparatus|

---

US8931703B1|2009-03-16|2015-01-13|Dynamics Inc.|Payment cards and devices for displaying barcodes|

---

US8566044B2|2009-03-16|2013-10-22|Apple Inc.|Event recognition|

---

US8302858B2|2009-03-24|2012-11-06|Eng U P Peter|Methods and systems for protecting credit card account information|

---

US20100250376A1|2009-03-31|2010-09-30|Srikanth Nandiraju|Virtual terminal for mobile devices|

---

JP5275883B2|2009-04-08|2013-08-28|株式会社エヌ・ティ・ティ・ドコモ|Client terminal linkage system, linkage server device, client terminal, client terminal linkage method|

---

US8060571B2|2009-04-15|2011-11-15|Sling Media, Inc.|Sharing of audio/visual content with a selected user|

---

US8157164B1|2009-04-16|2012-04-17|United Services Automobile Association |Systems and methods for providing financial card via automated teller machine|

---

US8131258B2|2009-04-20|2012-03-06|Boku, Inc.|Systems and methods to process transaction requests|

---

US20100272250A1|2009-04-28|2010-10-28|Michael Shen-Yuan Yap|Method and System for Pulling a Call|

---

EP2247087B1|2009-04-28|2011-08-24|Research In Motion Limited|Method and system for pulling a call|

---

AU2010244100B2|2009-05-03|2016-06-23|Smk-Logomotion Corporation|A payment terminal using a mobile communication device, such as a mobile phone; a method of direct debit payment transaction|

---

JP5388114B2|2009-05-19|2014-01-15|シャープ株式会社|Information communication system, communication apparatus, communication program, and communication method|

---

US9241062B2|2009-05-20|2016-01-19|Citrix Systems, Inc.|Methods and systems for using external display devices with a mobile computing device|

---

US9734496B2|2009-05-29|2017-08-15|Paypal, Inc.|Trusted remote attestation agent |

---

CN101567109B|2009-06-03|2012-01-04|普天信息技术研究院有限公司|Device integrating payment and gathering functions, system and trade method|

---

CN101576989A|2009-06-09|2009-11-11|阿里巴巴集团控股有限公司|Method for realizing payment in mobile terminal and mobile device|

---

KR101590357B1|2009-06-16|2016-02-01|엘지전자 주식회사|Operating a Mobile Terminal|

---

US8978130B2|2009-08-05|2015-03-10|Technology Policy Associates, Llc|Method and system for child authentication|

---

US9563350B2|2009-08-11|2017-02-07|Lg Electronics Inc.|Mobile terminal and method for controlling the same|

---

US8233272B2|2009-08-25|2012-07-31|Mindray Ds Usa, Inc.|Display units for use in monitoring patients and related systems and methods|

---

TWI554076B|2009-09-04|2016-10-11|普露諾洛股份有限公司|Remote phone manager|

---

US8412185B2|2009-09-14|2013-04-02|Nokia Corporation|Method and apparatus for switching devices using near field communication|

---

JP4738520B2|2009-09-18|2011-08-03|株式会社東芝|Electronic device and communication control method|

---

US8457651B2|2009-10-02|2013-06-04|Qualcomm Incorporated|Device movement user interface gestures for file sharing functionality|

---

US8799666B2|2009-10-06|2014-08-05|Synaptics Incorporated|Secure user authentication using biometric information|

---

TWI416366B|2009-10-12|2013-11-21|Htc Corp|Method, electronic apparatus and computer program product for creating biologic feature data|

---

KR101663474B1|2009-10-13|2016-10-10|삼성전자주식회사|A mobile terminal, method for displaying background in a mobile terminal and storage medium|

---

US8924893B2|2009-10-14|2014-12-30|At&T Mobility Ii Llc|Locking and unlocking of an electronic device using a sloped lock track|

---

JP5816677B2|2009-10-16|2015-11-18|日立オムロンターミナルソリューションズ株式会社|Biometric authentication device and biometric authentication method|

---

US8374916B2|2009-10-27|2013-02-12|At&T Mobility Ii Llc|Secure mobile-based financial transactions|

---

JP2011097287A|2009-10-28|2011-05-12|Nikon Corp|Camera|

---

US9832183B2|2011-04-19|2017-11-28|Early Warning Services, Llc|Key management using quasi out of band authentication architecture|

---

KR20110056099A|2009-11-20|2011-05-26|삼성전자주식회사|Digital imaging apparatus, method for controlling the same, and recording medium storing program to excute the method|

---

JP2011118662A|2009-12-03|2011-06-16|Toshiba Corp|Thin client type information processing system|

---

CA2889853C|2012-11-08|2017-02-21|Shalin Amin|Providing on-demand services through use of portable computing devices|

---

US8769428B2|2009-12-09|2014-07-01|Citrix Systems, Inc.|Methods and systems for generating a combined display of taskbar button group entries generated on a local machine and on a remote machine|

---

US20110142234A1|2009-12-15|2011-06-16|Michael Leonard Rogers|Multi-Factor Authentication Using a Mobile Phone|

---

US8411604B2|2009-12-21|2013-04-02|Research In Motion Limited|Methods and apparatus for use in facilitating access to aggregator services for mobile communication devices via wireless communication networks|

---

US8458780B1|2009-12-21|2013-06-04|Emc Corporation|Pluggable login architecture and dynamic resource recognition|

---

US8620213B2|2009-12-24|2013-12-31|Sony Computer Entertainment Inc.|Wireless device pairing methods|

---

US8805707B2|2009-12-31|2014-08-12|Hartford Fire Insurance Company|Systems and methods for providing a safety score associated with a user location|

---

US10169740B2|2009-12-31|2019-01-01|International Business Machines Corporation|Tag cloud buddy list for messaging contacts|

---

US9558520B2|2009-12-31|2017-01-31|Hartford Fire Insurance Company|System and method for geocoded insurance processing using mobile devices|

---

US20110163966A1|2010-01-06|2011-07-07|Imran Chaudhri|Apparatus and Method Having Multiple Application Display Modes Including Mode with Display Resolution of Another Apparatus|

---

JP2011141683A|2010-01-06|2011-07-21|Ricoh Co Ltd|Image processing apparatus, display device, authentication system, display control method, display control program and recording medium recording the same|

---

US20140122331A1|2010-01-08|2014-05-01|Blackhawk Network, Inc.|System and Method for Providing a Security Code|

---

US9318108B2|2010-01-18|2016-04-19|Apple Inc.|Intelligent automated assistant|

---

US9684394B2|2011-01-10|2017-06-20|Apple Inc.|Button functionality|

---

WO2013048880A1|2011-09-30|2013-04-04|Apple Inc.|Automatically adapting user interfaces for hands-free interaction|

---

US8744914B2|2010-01-28|2014-06-03|Bank Of America Corporation|Mobile device consumer interface process and system|

---

US20110201306A1|2010-02-15|2011-08-18|Samama Technologies|Systems and methods for unified billing|

---

FR2956502B1|2010-02-17|2012-02-10|Sagem Securite|METHOD AND DEVICE FOR DETECTING THE ORIENTATION OF A ZONE OF THE BODY OF AN INDIVIDUAL POSED ON AN AREA OF APPOSITION OF A SUPPORT OF A BIOMETRIC SENSOR|

---

CA2692677C|2010-02-26|2017-10-03|Xtreme Mobility Inc.|Secure billing system and method for a mobile device|

---

US9195926B2|2010-03-02|2015-11-24|Gonow Technologies, Llc|Portable e-wallet and universal card|

---

US20110218849A1|2010-03-03|2011-09-08|Rutigliano John R|Cloud platform for multiple account management & automated transaction processing|

---

US8464063B2|2010-03-10|2013-06-11|Avaya Inc.|Trusted group of a plurality of devices with single sign on, secure authentication|

---

US8892474B1|2010-03-11|2014-11-18|Bank Of America Corporation|Virtual purchasing card transaction|

---

US9741028B2|2010-03-11|2017-08-22|Wal-Mart Stores, Inc.|System and method for transaction payments using a mobile device|

---

JP2011197786A|2010-03-17|2011-10-06|Sony Corp|Information processing apparatus and information processing method|

---

JP2011209786A|2010-03-29|2011-10-20|Sony Corp|Information processor, information processing method, and program|

---

CN102209321B|2010-03-31|2013-10-09|华为终端有限公司|Switching processing method, communication system and associated equipment|

---

US9052925B2|2010-04-07|2015-06-09|Apple Inc.|Device, method, and graphical user interface for managing concurrently open software applications|

---

US9413836B2|2010-04-08|2016-08-09|At&T Intellectual Property I, L.P.|Communication routing based on presence in a confined wireless environment|

---

US8380177B2|2010-04-09|2013-02-19|Paydiant, Inc.|Mobile phone payment processing methods and systems|

---

US9400978B2|2010-04-09|2016-07-26|Paypal, Inc.|Methods and systems for selecting accounts and offers in payment transactions|

---

US10304051B2|2010-04-09|2019-05-28|Paypal, Inc.|NFC mobile wallet processing systems and methods|

---

KR20130101975A|2010-04-16|2013-09-16|니콜라스 제이 마스탄드리아|Wearable motion sensing computing interface|

---

US20110271181A1|2010-04-28|2011-11-03|Acer Incorporated|Screen unlocking method and electronic apparatus thereof|

---

US8494439B2|2010-05-04|2013-07-23|Robert Bosch Gmbh|Application state and activity transfer between devices|

---

KR101318958B1|2010-05-06|2013-10-29|시루정보|Method for payment service and device mobile communication terminal and transaction terminal|

---

JP5678468B2|2010-05-06|2015-03-04|株式会社リコー|Image processing system and operation management method|

---

KR101695810B1|2010-05-07|2017-01-13|엘지전자 주식회사|Mobile terminal and method for controlling thereof|

---

JP2011238125A|2010-05-12|2011-11-24|Sony Corp|Image processing device, method and program|

---

US20110281568A1|2010-05-13|2011-11-17|Rovi Technologies Corporation|Management of incoming telephony communications in a local media network|

---

EP2572314B1|2010-05-18|2020-10-14|Dynamics Inc.|Systems and methods for cards and devices operable to communicate via light pulses and touch sensitive displays|

---

WO2011146898A2|2010-05-21|2011-11-24|Bologh Mark J|Internet system for ultra high video quality|

---

KR101673925B1|2010-05-26|2016-11-09|삼성전자주식회사|Portable Device having the touch lock status and Operation system thereof|

---

US20110291971A1|2010-05-28|2011-12-01|Funai Electric Co., Ltd.|Highly Integrated Touch Screen Handheld Device|

---

US20110304556A1|2010-06-09|2011-12-15|Microsoft Corporation|Activate, fill, and level gestures|

---

JP4977236B2|2010-06-16|2012-07-18|株式会社東芝|Information terminal, launcher program and method|

---

JP5023193B2|2010-06-28|2012-09-12|株式会社東芝|Information processing device|

---

US9798822B2|2010-06-29|2017-10-24|Apple Inc.|Location based grouping of browsing histories|

---

US20110319056A1|2010-06-29|2011-12-29|Enterproid Hk Ltd|Remote access to a mobile device|

---

US8442914B2|2010-07-06|2013-05-14|Mastercard International Incorporated|Virtual wallet account with automatic-loading|

---

DE202010010266U1|2010-07-06|2010-10-14|Holzma Plattenaufteiltechnik Gmbh|Beamsaw|

---

US20120028609A1|2010-07-27|2012-02-02|John Hruska|Secure financial transaction system using a registered mobile device|

---

WO2012014304A1|2010-07-29|2012-02-02|富士通株式会社|Biometric authentication device and biometric authentication program|

---

US10580049B2|2011-04-05|2020-03-03|Ingenico, Inc.|System and method for incorporating one-time tokens, coupons, and reward systems into merchant point of sale checkout systems|

---

US8402533B2|2010-08-06|2013-03-19|Google Inc.|Input to locked computing device|

---

EP3021191B1|2010-08-13|2018-06-06|LG Electronics Inc.|Mobile terminal, display device, and control method therefor|

---

US8519834B2|2010-08-22|2013-08-27|Andrea Theresa Jersa|Wrist wound vibrating device|

---

US8854318B2|2010-09-01|2014-10-07|Nokia Corporation|Mode switching|

---

US8341142B2|2010-09-08|2012-12-25|Nuance Communications, Inc.|Methods and apparatus for searching the Internet|

---

WO2012033820A2|2010-09-08|2012-03-15|Nuance Communications, Inc.|Internet search related methods and apparatus|

---

US20120066731A1|2010-09-14|2012-03-15|Verizon Patent And Licensing Inc.|Customer service contact|

---

US8886710B2|2010-09-24|2014-11-11|Amazon Technologies, Inc.|Resuming content across devices and formats|

---

US8606948B2|2010-09-24|2013-12-10|Amazon Technologies, Inc.|Cloud-based device interaction|

---

US20120078751A1|2010-09-24|2012-03-29|Macphail William|Mobile device point of sale transaction system|

---

US20120078789A1|2010-09-29|2012-03-29|Ebay Inc.|Offline to online payment|

---

US8473577B2|2010-10-13|2013-06-25|Google Inc.|Continuous application execution between multiple devices|

---

US20120096386A1|2010-10-19|2012-04-19|Laurent Baumann|User interface for application transfers|

---

US20120123924A1|2010-10-20|2012-05-17|Mark Rose|Virtual currency configuration apparatuses, methods and systems|

---

WO2012058326A1|2010-10-26|2012-05-03|Modopayments, Llc|System and method for managing merchant-consumer interactions|

---

WO2015051361A1|2013-10-04|2015-04-09|Modopayments, Llc|System and method for managing merchant-consumer interactions|

---

US9262002B2|2010-11-03|2016-02-16|Qualcomm Incorporated|Force sensing touch screen|

---

JP5491357B2|2010-11-04|2014-05-14|ヤフー株式会社|Remittance system cooperation apparatus and method|

---

US8831677B2|2010-11-17|2014-09-09|Antony-Euclid C. Villa-Real|Customer-controlled instant-response anti-fraud/anti-identity theft devices , method and systems for secured global applications in personal/business e-banking, e-commerce, e-medical/health insurance checker, e-education/research/invention, e-disaster advisor, e-immigration, e-airport/aircraft security, e-military/e-law enforcement, with or without NFC component and system, with cellular/satellite phone/internet/multi-media functions|

---

KR101808625B1|2010-11-23|2018-01-18|엘지전자 주식회사|Content control apparatus and method thereof|

---

CN102004908B|2010-11-30|2012-10-17|汉王科技股份有限公司|Self-adapting face identification method and device|

---

US20120143694A1|2010-12-03|2012-06-07|Microsoft Corporation|Using behavioral data to manage computer services|

---

EP2649596B1|2010-12-09|2020-10-07|UTC Fire & Security Corporation|Wake-up circuit for a security device|

---

US20140156531A1|2010-12-14|2014-06-05|Salt Technology Inc.|System and Method for Authenticating Transactions Through a Mobile Device|

---

WO2012083113A2|2010-12-17|2012-06-21|Google Inc.|Digital wallet|

---

CN102096546A|2010-12-29|2011-06-15|华为终端有限公司|Unlocking method and device of operating system|

---

EP2659445A4|2010-12-30|2016-10-12|Mozido Corfire Korea Ltd|System and method for managing mobile wallet and its related credentials|

---

KR101830651B1|2011-01-04|2018-02-21|엘지전자 주식회사|Information displaying apparatus and method thereof|

---

US20140019352A1|2011-02-22|2014-01-16|Visa International Service Association|Multi-purpose virtual card transaction apparatuses, methods and systems|

---

CN102065148A|2011-01-12|2011-05-18|无锡网芯科技有限公司|Memory system access authorizing method based on communication network|

---

US8380637B2|2011-01-16|2013-02-19|Yerucham Levovitz|Variable fractions of multiple biometrics with multi-layer authentication of mobile transactions|

---

US20130030934A1|2011-01-28|2013-01-31|Zumigo, Inc.|System and method for credit card transaction approval based on mobile subscriber terminal location|

---

US8195576B1|2011-01-31|2012-06-05|Bank Of America Corporation|Mobile transaction device security system|

---

US8972286B2|2011-01-31|2015-03-03|Bank Of America Corporation|Transaction authorization system for a mobile commerce device|

---

US20120215553A1|2011-02-08|2012-08-23|Leston Jeff|Method and system of validating and verifying health care transactions|

---

EP2487871A1|2011-02-11|2012-08-15|Telefónica, S.A.|Method and system for transmission of application status between different devices|

---

US20120210226A1|2011-02-11|2012-08-16|Sony Network Entertainment International Llc|Method to playback a recently-played asset via a second display|

---

US20120209748A1|2011-02-12|2012-08-16|The Penn State Research Foundation|Devices, systems, and methods for providing gift selection and gift redemption services in an e-commerce environment over a communication network|

---

US20120209749A1|2011-02-16|2012-08-16|Ayman Hammad|Snap mobile payment apparatuses, methods and systems|

---

US20120215647A1|2011-02-22|2012-08-23|Powell Ken R|Systems and methods for promoting products and services|

---

US9971998B2|2011-02-25|2018-05-15|Paypal, Inc.|Location-based automatic payment system|

---

US20120222092A1|2011-02-25|2012-08-30|Qualcomm Incorporated|Controlling access to media for an electronic device|

---

US20120221464A1|2011-02-28|2012-08-30|Research In Motion Limited|Communications system for performing secure transactions based upon mobile wireless communications device proximity and related methods|

---

EP2681708A4|2011-03-02|2014-09-03|Pxt Payment Inc|Mobile payment and point system and method|

---

JP6034551B2|2011-03-16|2016-11-30|任天堂株式会社|Information processing system, information processing apparatus, information processing program, and image display method|

---

US8392259B2|2011-03-17|2013-03-05|Research In Motion Limited|Methods and apparatus to obtain transaction confirmation|

---

WO2012126078A1|2011-03-23|2012-09-27|Research In Motion Limited|Method for conference call prompting from a locked device|

---

WO2012128466A1|2011-03-24|2012-09-27|Danal Co.,Ltd.|Method of controlling system and mobile device for processing payment data|

---

WO2012135115A2|2011-03-25|2012-10-04|Visa International Service Association|In-person one-tap purchasing apparatuses, methods and systems|

---

EP2801065A4|2012-01-05|2015-08-05|Visa Int Service Ass|Transaction visual capturing apparatuses, methods and systems|

---

US10630795B2|2011-03-31|2020-04-21|Oath Inc.|Systems and methods for transferring application state between devices based on gestural input|

---

JP2012215981A|2011-03-31|2012-11-08|Toshiba Tec Corp|Settlement device and program|

---

US9337999B2|2011-04-01|2016-05-10|Intel Corporation|Application usage continuum across platforms|

---

US8938312B2|2011-04-18|2015-01-20|Sonos, Inc.|Smart line-in processing|

---

US9225701B2|2011-04-18|2015-12-29|Intelmate Llc|Secure communication systems and methods|

---

EP2702752B1|2011-04-27|2019-09-18|BlackBerry Limited|System and method for automatically answering a call on a communication device|

---

DK2702546T3|2011-04-29|2021-03-15|American Greetings Corp|Systems, methods and apparatuses for creating, editing, distributing and viewing electronic greeting cards|

---

US9606643B2|2011-05-02|2017-03-28|Microsoft Technology Licensing, Llc|Extended above the lock-screen experience|

---

US10222974B2|2011-05-03|2019-03-05|Nokia Technologies Oy|Method and apparatus for providing quick access to device functionality|

---

US9229489B2|2011-05-03|2016-01-05|Facebook, Inc.|Adjusting mobile device state based on user intentions and/or identity|

---

US10402898B2|2011-05-04|2019-09-03|Paypal, Inc.|Image-based financial processing|

---

US9141616B2|2011-05-06|2015-09-22|Google Inc.|Physical confirmation for network-provided content|

---

US8812601B2|2011-05-09|2014-08-19|Google Inc.|Transferring application state across devices with checkpoints|

---

US8171137B1|2011-05-09|2012-05-01|Google Inc.|Transferring application state across devices|

---

US8224894B1|2011-05-09|2012-07-17|Google Inc.|Zero-click sharing of application context across devices|

---

US10949844B2|2011-05-09|2021-03-16|Intuit Inc.|Processing electronic payment involving mobile communication device|

---

US20120290943A1|2011-05-10|2012-11-15|Nokia Corporation|Method and apparatus for distributively managing content between multiple users|

---

EP2707847A4|2011-05-10|2015-04-01|Dynamics Inc|Systems, devices, and methods for mobile payment acceptance, mobile authorizations, mobile wallets, and contactless communication mechanisms|

---

US20120297017A1|2011-05-20|2012-11-22|Microsoft Corporation|Privacy-conscious personalization|

---

US20120310760A1|2011-06-03|2012-12-06|Simon Phillips|Mobile device automatic card account selection for a transaction|

---

US9292310B2|2011-06-05|2016-03-22|Apple Inc.|Systems and methods for displaying notifications received from multiple applications|

---

US20120316933A1|2011-06-09|2012-12-13|Massachusetts Institute Of Technology|Method for promoting behavior change through social reward mediation|

---

KR101805178B1|2011-06-10|2017-12-05|엘지전자 주식회사|Mobile terminal and control method therof|

---

KR101121440B1|2011-06-16|2012-03-16|에이큐 주식회사|Mobile phone using nfc and control method thereof|

---

KR101121441B1|2011-06-16|2012-03-16|에이큐 주식회사|Mobile phone using nfc and control method thereof|

---

US9891800B2|2011-06-17|2018-02-13|Nokia Technologies Oy|Method and apparatus for providing a notification mechanism|

---

US20140094143A1|2011-06-28|2014-04-03|The Boeing Company|Passenger mobile station registration with a passenger communications system using near field communicaitons|

---

US8663018B2|2011-06-29|2014-03-04|Amazon Technologies, Inc.|Data locker synchronization|

---

TW201301118A|2011-06-30|2013-01-01|Gcca Inc|Cloud-based communication device and smart mobile device using cloud-based communication device|

---

US20130006746A1|2011-06-30|2013-01-03|Ncr Corporation|Techniques for integrating social networking rewards with the retail checkout process|

---

WO2013000150A1|2011-06-30|2013-01-03|Nokia Corporation|Method, apparatus and computer program product for retrieval of lost or forgotten passwords|

---

US9582598B2|2011-07-05|2017-02-28|Visa International Service Association|Hybrid applications utilizing distributed models and views apparatuses, methods and systems|

---

US10121129B2|2011-07-05|2018-11-06|Visa International Service Association|Electronic wallet checkout platform apparatuses, methods and systems|

---

JP5762186B2|2011-07-12|2015-08-12|株式会社日本総合研究所|Card unauthorized use prevention system and card unauthorized use prevention method|

---

US8827153B1|2011-07-18|2014-09-09|Dynamics Inc.|Systems and methods for waveform generation for dynamic magnetic stripe communications devices|

---

US8726371B2|2011-07-18|2014-05-13|Cisco Technology, Inc.|Enhanced security for devices enabled for wireless communications|

---

US20130027289A1|2011-07-27|2013-01-31|Lg Electronics Inc.|Electronic device|

---

US9071418B2|2011-07-29|2015-06-30|Blackfire Research Corporation|Synchronous media rendering of demuxed media components across multiple devices|

---

US9438697B2|2011-08-01|2016-09-06|Quickbiz Holdings Limited, Apia|User interface content state synchronization across devices|

---

JP5818563B2|2011-08-02|2015-11-18|株式会社東光高岳|Charging system for electric mobile object, charging device for electric mobile object, portable communication terminal and server device included therein, and charging method for electric mobile object|

---

US9355394B2|2011-08-11|2016-05-31|Visa International Service Association|Systems and methods of aggregating split payments using a settlement ecosystem|

---

US20130041790A1|2011-08-12|2013-02-14|Sivakumar Murugesan|Method and system for transferring an application state|

---

US8788881B2|2011-08-17|2014-07-22|Lookout, Inc.|System and method for mobile device push communications|

---

US9864632B2|2011-08-17|2018-01-09|Open Invention Network, Llc|System and method for transfer of an application state between devices|

---

CA2844768A1|2011-08-17|2013-02-21|Trans Union Llc|Systems and methods for generating vehicle insurance premium quotes based on a vehicle history|

---

US9355393B2|2011-08-18|2016-05-31|Visa International Service Association|Multi-directional wallet connector apparatuses, methods and systems|

---

US10372712B2|2011-08-18|2019-08-06|Visa International Service Association|Converged merchant processing apparatuses, methods and systems|

---

US8789156B2|2011-08-19|2014-07-22|International Business Machines Corporation|Data management with a networked mobile device|

---

US8750677B2|2011-08-23|2014-06-10|Microsoft Corporation|Method for transferring media playback from a different device|

---

KR101419984B1|2011-08-26|2014-07-15|주식회사 팬택|System and method for sharing content suing nfc in cloud circumstance|

---

EP2748927B1|2011-08-26|2017-05-17|Azoteq Limited|Intelligent capacitive swipe switch|

---

US8806369B2|2011-08-26|2014-08-12|Apple Inc.|Device, method, and graphical user interface for managing and interacting with concurrently open software applications|

---

US20130060678A1|2011-09-06|2013-03-07|Rawllin International Inc.|Electronic payment systems and supporting methods and devices|

---

KR101719994B1|2011-09-07|2017-03-27|엘지전자 주식회사|Mobile terminal and method for controlling the same|

---

JP2013058828A|2011-09-07|2013-03-28|Jvc Kenwood Corp|Smile determination device and method|

---

US10489570B2|2011-09-09|2019-11-26|Google Llc|Preventing computing device from timing out|

---

US8976128B2|2011-09-12|2015-03-10|Google Technology Holdings LLC|Using pressure differences with a touch-sensitive display screen|

---

US8769286B2|2011-09-20|2014-07-01|Daon Holdings Limited|Methods and systems for increasing the security of electronic messages|

---

US20130073286A1|2011-09-20|2013-03-21|Apple Inc.|Consolidating Speech Recognition Results|

---

US9286384B2|2011-09-21|2016-03-15|Sonos, Inc.|Methods and systems to share media|

---

US20130080275A1|2011-09-23|2013-03-28|Bank Of America Corporation|Transaction device and processing system|

---

US20130080272A1|2011-09-23|2013-03-28|Bank Of America Corporation|Transaction device and processing system|

---

US9052810B2|2011-09-28|2015-06-09|Sonos, Inc.|Methods and apparatus to manage zones of a multi-zone media playback system|

---

US8762156B2|2011-09-28|2014-06-24|Apple Inc.|Speech recognition repair using contextual information|

---

US8769624B2|2011-09-29|2014-07-01|Apple Inc.|Access control utilizing indirect authentication|

---

US9576284B2|2011-09-29|2017-02-21|Paypal, Inc.|Social proximity payments|

---

US9002322B2|2011-09-29|2015-04-07|Apple Inc.|Authentication with secondary approver|

---

US8880055B1|2011-10-06|2014-11-04|Marvell International Ltd.|Method and apparatus for using near field communication to performtransactions on a mobile device|

---

US9031540B2|2011-10-07|2015-05-12|Newaer Inc.|Automatication of a user transaction based upon scanned wireless signals|

---

CN103037064B|2011-10-08|2015-02-11|英华达（上海）科技有限公司|Individual screen unlocking method and system thereof|

---

US8917877B2|2011-10-12|2014-12-23|Sony Corporation|Distance-based rendering of media files|

---

US20140207680A1|2011-10-17|2014-07-24|Capital One Financial Corporation|System and method for providing a mobile wallet shopping companion application|

---

US20160180305A1|2011-10-24|2016-06-23|Bc Investments & Leasing, Inc.|Payment Method Linked To A Mobile Number|

---

US8718628B2|2011-10-24|2014-05-06|Verizon Patent And Licensing Inc.|Intelligent call identification|

---

US9305312B2|2011-10-25|2016-04-05|Theodosios Kountotsis|Express easy-pass checkout at grocery stores and retail establishments for preferred members|

---

JP5739303B2|2011-10-25|2015-06-24|京セラ株式会社|Mobile terminal, lock control program, and lock control method|

---

US20130110675A1|2011-10-31|2013-05-02|Microsoft Corporation|Marketplace for Composite Application and Data Solutions|

---

US10510056B2|2011-11-02|2019-12-17|Mastercard International Incorporated|Method and system for multiple payment applications|

---

US8639230B2|2011-11-04|2014-01-28|Google Inc.|Transferring an active call to another device|

---

US8225191B1|2011-11-07|2012-07-17|Google Inc.|Synchronizing web browsers|

---

US8719734B2|2011-11-16|2014-05-06|Microsoft Corporation|Two-stage swipe gesture recognition|

---

US9526127B1|2011-11-18|2016-12-20|Google Inc.|Affecting the behavior of a user device based on a user's gaze|

---

US9661073B2|2011-11-18|2017-05-23|Google Inc.|Web browser synchronization with multiple simultaneous profiles|

---

WO2013075071A1|2011-11-18|2013-05-23|Ayman Hammad|Mobile wallet store and service injection platform apparatuses, methods and systems|

---

US20130174044A1|2011-11-22|2013-07-04|Thomas Casey Hill|Methods and apparatus to control presentation devices|

---

JP5869316B2|2011-11-25|2016-02-24|京セラ株式会社|Portable electronic devices|

---

TWI487364B|2011-12-01|2015-06-01|Amtran Technology Co Ltd|Method for switching calls between devices and communication device|

---

US20130144738A1|2011-12-01|2013-06-06|Spenzi, Inc.|Gifting and Sharing Using SMS Messages for Shared Coupon/Gift-Card Auto-Redemption and Multi-Source Payment from Buyer's Mobile Phone|

---

US10169822B2|2011-12-02|2019-01-01|Spireon, Inc.|Insurance rate optimization through driver behavior monitoring|

---

US8392617B1|2011-12-06|2013-03-05|Google Inc.|Browsing context continuation across multiple devices|

---

US9246543B2|2011-12-12|2016-01-26|Futurewei Technologies, Inc.|Smart audio and video capture systems for data processing systems|

---

CN103164791B|2011-12-13|2016-04-06|阿里巴巴集团控股有限公司|A kind of method and apparatus being realized secure payment by electric terminal|

---

US9015066B2|2011-12-13|2015-04-21|Ebay Inc.|Digital wallet loading|

---

US20130159178A1|2011-12-14|2013-06-20|Firethorn Mobile, Inc.|System and Method For Loading A Virtual Token Managed By A Mobile Wallet System|

---

TW201324310A|2011-12-14|2013-06-16|Acer Inc|Method for unlocking screen|

---

US9245020B2|2011-12-14|2016-01-26|Microsoft Technology Licensing, Llc|Collaborative media sharing|

---

US20130166325A1|2011-12-23|2013-06-27|Mohan Ganapathy|Apparatuses, systems and methods for insurance quoting|

---

KR101679343B1|2011-12-28|2016-11-24|노키아 테크놀로지스 오와이|Application switcher|

---

JP6034401B2|2011-12-28|2016-11-30|ノキア テクノロジーズ オーユー|Providing an open instance of the application|

---

JP2015508535A|2011-12-29|2015-03-19|インテル・コーポレーション|Virtual point of sale management|

---

US9247492B2|2011-12-29|2016-01-26|Sonos, Inc.|Systems and methods for multi-network audio control|

---

US9191699B2|2011-12-29|2015-11-17|Sonos, Inc.|Systems and methods for connecting an audio controller to a hidden audio network|

---

US20130223696A1|2012-01-09|2013-08-29|Sensible Vision, Inc.|System and method for providing secure access to an electronic device using facial biometric identification and screen gesture|

---

KR20130082190A|2012-01-11|2013-07-19|엘지전자 주식회사|Terminal and method for diaplaying icons|

---

US20130179304A1|2012-01-11|2013-07-11|Jason Swist|Method and system for notifications relating to consumer actions|

---

US9372978B2|2012-01-20|2016-06-21|Apple Inc.|Device, method, and graphical user interface for accessing an application in a locked device|

---

JP5715968B2|2012-01-23|2015-05-13|富士通フロンテック株式会社|Bidding apparatus, bidding system, and bidding method|

---

US9436929B2|2012-01-24|2016-09-06|Verizon Patent And Licensing Inc.|Collaborative event playlist systems and methods|

---

WO2013111239A1|2012-01-26|2013-08-01|パナソニック株式会社|Mobile terminal, television broadcast receiver, and device linkage method|

---

US20130198112A1|2012-01-30|2013-08-01|Verizon Patent And Licensing Inc.|Capacity Management Methods and Systems|

---

WO2013115748A1|2012-01-30|2013-08-08|Echostar Ukraine, L.L.C.|Apparatus, systems and methods for adjusting output audio volume based on user location|

---

JP5906097B2|2012-01-31|2016-04-20|キヤノン株式会社|Electronic device, its control method, program, and recording medium|

---

WO2013116726A1|2012-02-03|2013-08-08|Ebay Inc.|Adding card to mobile wallet using nfc|

---

US9680927B2|2012-02-05|2017-06-13|Apple Inc.|Cloud tabs|

---

US9507630B2|2012-02-09|2016-11-29|Cisco Technology, Inc.|Application context transfer for distributed computing resources|

---

US8995960B2|2012-02-10|2015-03-31|Dedo Interactive, Inc.|Mobile device authentication|

---

WO2013123438A1|2012-02-15|2013-08-22|Blackhawk Network, Inc|System and method of registering stored-value cards into electronic wallets|

---

KR101443960B1|2012-02-22|2014-11-03|주식회사 팬택|Electronic device and method for user identification|

---

US9767453B2|2012-02-23|2017-09-19|XRomb Inc.|System and method for processing payment during an electronic commerce transaction|

---

US8763896B2|2012-02-23|2014-07-01|XRomb Inc.|System and method of loading a transaction card and processing repayment on a mobile device|

---

KR102008495B1|2012-02-24|2019-08-08|삼성전자주식회사|Method for sharing content and mobile terminal thereof|

---

US9778706B2|2012-02-24|2017-10-03|Blackberry Limited|Peekable user interface on a portable electronic device|

---

US8947382B2|2012-02-28|2015-02-03|Motorola Mobility Llc|Wearable display device, corresponding systems, and method for presenting output on the same|

---

KR102088451B1|2012-02-29|2020-03-12|모비웨이브 인코포레이티드|Method, device and secure element for conducting a secured financial transaction on a device|

---

EP2823438A4|2012-03-05|2015-05-06|Visa Int Service Ass|Authentication using biometric technology through a consumer device|

---

US9936329B2|2012-03-09|2018-04-03|Nokia Technologies Oy|Methods, apparatuses, and computer program products for operational routing between proximate devices|

---

US8725113B2|2012-03-12|2014-05-13|Google Inc.|User proximity control of devices|

---

WO2013135270A1|2012-03-13|2013-09-19|Telefonaktiebolaget L M Ericsson |An apparatus and method for navigating on a touch sensitive screen thereof|

---

US9105021B2|2012-03-15|2015-08-11|Ebay, Inc.|Systems, methods, and computer program products for using proxy accounts|

---

US8751577B2|2012-03-15|2014-06-10|Google Inc.|Methods and systems for ordering and voting on shared media playlists|

---

US9177130B2|2012-03-15|2015-11-03|Google Inc.|Facial feature detection|

---

US10469897B2|2012-03-19|2019-11-05|Sonos, Inc.|Context-based user music menu systems and methods|

---

US9305310B2|2012-03-19|2016-04-05|Uber Technologies, Inc.|Enabling a user to verify a price change for an on-demand service|

---

JP6098898B2|2012-03-27|2017-03-22|パナソニックＩｐマネジメント株式会社|Electrical device and method for controlling electrical device|

---

CA2866500C|2012-04-01|2016-08-30|Authentify, Inc.|Secure authentication in a multi-party system|

---

KR20120040693A|2012-04-09|2012-04-27|주식회사 비즈모델라인|Method for setting payment means|

---

JP2012168966A|2012-04-10|2012-09-06|Toshiba Corp|Information terminal, and program and method thereof|

---

US8583549B1|2012-04-10|2013-11-12|Hossein Mohsenzadeh|Systems, devices, and methods for managing a payment transaction|

---

GB201206564D0|2012-04-13|2012-05-30|Intrasonics Sarl|Event engine synchronisation|

---

US8254647B1|2012-04-16|2012-08-28|Google Inc.|Facial image quality assessment|

---

CN102663303A|2012-04-17|2012-09-12|李凯|Method for exercising permission by mobile equipment|

---

JP2013222410A|2012-04-18|2013-10-28|Fujitsu Frontech Ltd|Portable terminal having non-contact ic card function and program therefor|

---

US20130282533A1|2012-04-18|2013-10-24|Elizabeth Foran-Owens|Providing an online consumer shopping experience in-store|

---

US20130282577A1|2012-04-19|2013-10-24|Benjamin P. Milne|Social network transaction processing system|

---

EP2654275A1|2012-04-21|2013-10-23|BlackBerry Limited|System and method for transmitting application databetween two communication devices|

---

US20130283199A1|2012-04-24|2013-10-24|Microsoft Corporation|Access to an Application Directly from a Lock Screen|

---

CN102707994B|2012-04-27|2014-08-20|西安电子科技大学|Method for controlling computer by handheld mobile equipment in local area network|

---

US20170372405A9|2012-05-04|2017-12-28|Kachyng, Inc.|Quick transaction completion using mobile device|

---

US20130297414A1|2012-05-07|2013-11-07|Flint Mobile, Inc.|Method, apparatus, and computer-readable medium for managing mobile payment transactions|

---

US20130304514A1|2012-05-08|2013-11-14|Elwha Llc|Systems and methods for insurance based on monitored characteristics of an autonomous drive mode selection system|

---

DE112013002387T5|2012-05-09|2015-02-12|Apple Inc.|Apparatus, method and graphical user interface for providing tactile feedback for operations in a user interface|

---

KR101956082B1|2012-05-09|2019-03-11|애플 인크.|Device, method, and graphical user interface for selecting user interface objects|

---

WO2013169842A2|2012-05-09|2013-11-14|Yknots Industries Llc|Device, method, and graphical user interface for selecting object within a group of objects|

---

US10235014B2|2012-05-09|2019-03-19|Apple Inc.|Music user interface|

---

US9953310B2|2012-05-10|2018-04-24|Mastercard International Incorporated|Systems and method for providing multiple virtual secure elements in a single physical secure element of a mobile device|

---

US9280610B2|2012-05-14|2016-03-08|Apple Inc.|Crowd sourcing information to fulfill user requests|

---

US9053293B2|2012-05-15|2015-06-09|Sap Se|Personal authentications on computing devices|

---

US10417037B2|2012-05-15|2019-09-17|Apple Inc.|Systems and methods for integrating third party services with a digital assistant|

---

US9086937B2|2012-05-16|2015-07-21|Apple Inc.|Cloud-based application resource files|

---

US20130311597A1|2012-05-16|2013-11-21|Apple Inc.|Locally backed cloud-based storage|

---

CN111176516A|2012-05-18|2020-05-19|苹果公司|Device, method and graphical user interface for manipulating a user interface|

---

WO2013177548A1|2012-05-24|2013-11-28|Paydiant , Inc.|Method and systems for wallet enrollment|

---

US8850037B2|2012-05-24|2014-09-30|Fmr Llc|Communication session transfer between devices|

---

CN102737313A|2012-05-25|2012-10-17|天地融科技股份有限公司|Method and system for authorizing verification on electronic signature tools and electronic signature tools|

---

CN103458215B|2012-05-29|2016-11-23|国基电子（上海）有限公司|System, mobile phone, electronic installation and the changing method of Switch Video call|

---

CN102750086A|2012-05-31|2012-10-24|上海必邦信息科技有限公司|Method for achieving control of wirelessly shared and displayed pages between electronic devices|

---

US9690465B2|2012-06-01|2017-06-27|Microsoft Technology Licensing, Llc|Control of remote applications using companion device|

---

US10156455B2|2012-06-05|2018-12-18|Apple Inc.|Context-aware voice guidance|

---

US10354004B2|2012-06-07|2019-07-16|Apple Inc.|Intelligent presentation of documents|

---

US10025920B2|2012-06-07|2018-07-17|Early Warning Services, Llc|Enterprise triggered 2CHK association|

---

US10019994B2|2012-06-08|2018-07-10|Apple Inc.|Systems and methods for recognizing textual identifiers within a plurality of words|

---

KR102071692B1|2012-06-11|2020-01-31|삼성전자주식회사|Mobile device and control method thereof|

---

EP2674889B1|2012-06-11|2018-05-30|Samsung Electronics Co., Ltd|Mobile device and control method thereof|

---

US20130332358A1|2012-06-12|2013-12-12|Ebay, Inc.|Fraud detection system|

---

US8842888B2|2012-06-15|2014-09-23|Aoptix Technologies, Inc.|User interface for combined biometric mobile device|

---

US8441548B1|2012-06-15|2013-05-14|Google Inc.|Facial image quality assessment|

---

US20130346302A1|2012-06-20|2013-12-26|Visa International Service Association|Remote Portal Bill Payment Platform Apparatuses, Methods and Systems|

---

US10073541B1|2012-06-22|2018-09-11|Amazon Technologies, Inc.|Indicators for sensor occlusion|

---

US20130346068A1|2012-06-25|2013-12-26|Apple Inc.|Voice-Based Image Tagging and Searching|

---

US8396265B1|2012-06-26|2013-03-12|Google Inc.|Facial recognition|

---

US9374607B2|2012-06-26|2016-06-21|Sonos, Inc.|Media playback system with guest access|

---

KR101887061B1|2012-06-27|2018-08-09|엘지전자 주식회사|Mobile terminal and method for controlling the same|

---

US9247068B2|2012-06-27|2016-01-26|Blackberry Limited|Apparatus, system and method of call notifications to active communication devices|

---

JP6050625B2|2012-06-28|2016-12-21|サターン ライセンシング エルエルシーＳａｔｕｒｎ Ｌｉｃｅｎｓｉｎｇ ＬＬＣ|Information processing apparatus and information processing method, computer program, and information communication system|

---

US9202099B2|2012-06-29|2015-12-01|Apple Inc.|Fingerprint sensing and enrollment|

---

US9767446B2|2012-07-19|2017-09-19|Mastercard International Incorporated|Touch screen system and methods for multiple contactless payments|

---

US20140026188A1|2012-07-23|2014-01-23|Justin L. Gubler|Systems, methods, and devices for restricting use of electronic devices based on proximity to wireless devices|

---

US8990343B2|2012-07-30|2015-03-24|Google Inc.|Transferring a state of an application from a first computing device to a second computing device|

---

US8995687B2|2012-08-01|2015-03-31|Sonos, Inc.|Volume interactions for connected playback devices|

---

US20140036099A1|2012-08-03|2014-02-06|Be Labs, Llc|Automated Scanning|

---

KR101458179B1|2012-08-03|2014-11-04|김만근|Integrated electronic management system and management method thereof|

---

US8930005B2|2012-08-07|2015-01-06|Sonos, Inc.|Acoustic signatures in a playback system|

---

US9736265B2|2012-08-09|2017-08-15|Facebook, Inc.|Handling notifications|

---

US9779396B2|2012-08-14|2017-10-03|Chijioke Chukwuemeka UZO|Method of making mobile payments to a recipient lacking a wireless or contactless terminal|

---

CN102843681A|2012-08-15|2012-12-26|腾讯科技（深圳）有限公司|Information interaction method and information interaction device|

---

KR101971911B1|2012-08-16|2019-04-24|삼성전자주식회사|Method for displaying for image and an electronic device thereof|

---

US20140058935A1|2012-08-21|2014-02-27|Noel Mijares|Mobile contactless digital watch payment|

---

WO2014030875A1|2012-08-24|2014-02-27|Samsung Electronics Co., Ltd.|Apparatus and method for providing interaction information by using image on device display|

---

KR102174437B1|2012-08-24|2020-11-04|삼성전자주식회사|Apparatus and method for providing interaction information by using image on device display|

---

US20140058939A1|2012-08-24|2014-02-27|Ebay Inc.|Method and apparatus for processing payment transactions from a chat application integrated with a payment application that leverages social features from the chat application|

---

JP6051681B2|2012-08-24|2016-12-27|ソニー株式会社|Information processing apparatus, information processing method, and program|

---

WO2014030876A1|2012-08-24|2014-02-27|Samsung Electronics Co., Ltd.|Method and apparatus for determining item based on interaction environment|

---

CN102866828B|2012-08-29|2015-11-25|腾讯科技（深圳）有限公司|A kind of terminal control method and equipment|

---

JP6069328B2|2012-08-31|2017-02-01|楽天Ｅｄｙ株式会社|Portable terminal, portable terminal control method, program, and recording medium|

---

TWI619067B|2012-08-31|2018-03-21|財團法人資訊工業策進會|Screen unlocking method with time information, unlocking system and recording medium|

---

US8560004B1|2012-08-31|2013-10-15|Google Inc.|Sensor-based activation of an input device|

---

GB2505476B|2012-08-31|2019-02-27|Metaswitch Networks Ltd|Processing communication sessions|

---

US8826415B2|2012-09-04|2014-09-02|Apple Inc.|Automated device access|

---

CN104756135B|2012-09-05|2018-11-23|埃利蒙特公司|System and method for biological characteristic validation relevant to the equipment equipped with camera|

---

US9069469B2|2012-09-10|2015-06-30|Apple Inc.|Sharing and synchronizing data across users of cloud computing systems|

---

US9282893B2|2012-09-11|2016-03-15|L.I.F.E. Corporation S.A.|Wearable communication platform|

---

US20140090045A1|2012-09-11|2014-03-27|First Data Corporation|Systems and methods for facilitating login aid functionality in mobile commerce|

---

US10235672B2|2012-09-12|2019-03-19|Zukunftware, Llc|Securely receiving from a remote user sensitive information and authorization to perform a transaction using the sensitive information|

---

US8769651B2|2012-09-19|2014-07-01|Secureauth Corporation|Mobile multifactor single-sign-on authentication|

---

WO2014052474A1|2012-09-25|2014-04-03|Google Inc.|Securing personal identification numbers for mobile payment applications by combining with random components|

---

US9251787B1|2012-09-26|2016-02-02|Amazon Technologies, Inc.|Altering audio to improve automatic speech recognition|

---

KR102001913B1|2012-09-27|2019-07-19|엘지전자 주식회사|Mobile Terminal and Operating Method for the Same|

---

JP5964190B2|2012-09-27|2016-08-03|京セラ株式会社|Terminal device|

---

US9100828B2|2012-09-30|2015-08-04|Apple Inc.|Transferring data over Bluetooth using intermediary bridge|

---

US9600552B2|2012-10-02|2017-03-21|Nextbit Systems Inc.|Proximity based application state synchronization|

---

WO2014055459A1|2012-10-03|2014-04-10|Redbox Automated Retail, Llc|System and method for event ticketing utilizing an article dispensing machine|

---

EP2717552A1|2012-10-04|2014-04-09|Nagravision S.A.|A portable proximity wireless communication device|

---

TWI490773B|2012-10-09|2015-07-01|Ind Tech Res Inst|An user interface operating method and an electrical device with the user interfaceand a program product storing a program for operating the user interface|

---

US9792035B2|2012-10-09|2017-10-17|Mastercard International Incorporated|System and method for payment using a mobile device|

---

US9053340B2|2012-10-12|2015-06-09|Citrix Systems, Inc.|Enterprise application store for an orchestration framework for connected devices|

---

US9147058B2|2012-10-12|2015-09-29|Apple Inc.|Gesture entry techniques|

---

TW201416959A|2012-10-16|2014-05-01|Yun-Heng Shiu|Webpage interface|

---

US20160019536A1|2012-10-17|2016-01-21|Royal Bank Of Canada|Secure processing of data|

---

US8942420B2|2012-10-18|2015-01-27|Qualcomm Incorporated|Detecting embossed characters on form factor|

---

KR20140051640A|2012-10-23|2014-05-02|삼성전자주식회사|Financial transaction method of mobile equipment, apparatus thereof, and medium storing program source thereof|

---

US9575650B2|2012-10-26|2017-02-21|Htc Corporation|Mobile communications device, non-transitory computer-readable medium and method of switching screen of mobile communications device from screen locked state to screen unlocked state|

---

US10140537B2|2012-10-26|2018-11-27|Daon Holdings Limited|Methods and systems for capturing biometric data|

---

US8963806B1|2012-10-29|2015-02-24|Google Inc.|Device authentication|

---

US9277017B2|2012-10-30|2016-03-01|Netiq Corporation|Techniques for device independent session migration|

---

KR101448547B1|2012-10-31|2014-10-08|에스케이씨앤씨 주식회사|Method and System for Application Integrated Management|

---

US20140129441A1|2012-11-02|2014-05-08|German Blanco|Systems and methods for authorizing sensitive purchase transactions with a mobile device|

---

US11222329B2|2012-11-05|2022-01-11|Mastercard International Incorporated|Electronic wallet apparatus, method, and computer program product|

---

US9258693B2|2012-11-09|2016-02-09|Apple Inc.|Device centric or interactive discovery|

---

US9250660B2|2012-11-14|2016-02-02|Laserlock Technologies, Inc.|“HOME” button with integrated user biometric sensing and verification system for mobile device|

---

US9038894B2|2012-11-20|2015-05-26|Cellco Partnership|Payment or other transaction through mobile device using NFC to access a contactless transaction card|

---

US9947011B2|2012-11-20|2018-04-17|Paypal, Inc.|Environment and methods for enabling electronic transactions|

---

WO2014078965A1|2012-11-22|2014-05-30|8303142 Canada Inc.|System and method for managing several mobile devices simultaneously|

---

GB201221103D0|2012-11-23|2013-01-09|Islam Saidul|Payepos card or payepos top up card|

---

US20140149884A1|2012-11-26|2014-05-29|William Joseph Flynn, III|User-Based Interactive Elements|

---

KR101912445B1|2012-11-28|2018-10-26|주식회사 케이티|Method and Apparatus for providing payment interface in a portable electronic device|

---

US9549323B2|2012-12-03|2017-01-17|Samsung Electronics Co., Ltd.|Method and mobile terminal for controlling screen lock|

---

US20140164082A1|2012-12-06|2014-06-12|Capital One Financial Corporation|Systems and methods for social media referrals based rewards|

---

WO2014088470A2|2012-12-07|2014-06-12|Yota Devices Ipr Limited|Haptic message|

---

WO2014089763A1|2012-12-12|2014-06-19|Intel Corporation|Single- gesture device unlock and application launch|

---

US9098177B2|2012-12-13|2015-08-04|Google Technology Holdings LLC|Apparatus and methods for facilitating context handoff between devices in a cloud based wireless personal area network|

---

US9185742B2|2012-12-13|2015-11-10|Google Technology Holdings LLC|System and methods for a cloud based wireless personal area network service enabling context activity handoffs between devices|

---

US20150243163A1|2012-12-14|2015-08-27|Biscotti Inc.|Audio Based Remote Control Functionality|

---

JP5780235B2|2012-12-18|2015-09-16|コニカミノルタ株式会社|Information processing system, information processing apparatus, program, and portable terminal device|

---

KR20140080146A|2012-12-20|2014-06-30|삼성전자주식회사|Method for displaying for content using history an electronic device thereof|

---

US9710628B2|2012-12-21|2017-07-18|Nokia Technologies Oy|Unlocking an apparatus|

---

KR101330962B1|2012-12-27|2013-11-18|신한카드 주식회사|Payment device control method for selecting card settlement|

---

US8762272B1|2012-12-27|2014-06-24|Google Inc.|Management of emails containing payments|

---

JP6080548B2|2012-12-28|2017-02-15|キヤノン株式会社|COMMUNICATION DEVICE, INFORMATION TERMINAL, ITS CONTROL METHOD, PROGRAM|

---

US10320803B2|2012-12-28|2019-06-11|Dish Technologies Llc|Determining eligibility for multiple client media streaming|

---

US10600128B2|2012-12-29|2020-03-24|Robert William Graham|Mobile expense report system|

---

US20140244365A1|2012-12-29|2014-08-28|DGRT Software LLC|Toll app system|

---

CN104903835B|2012-12-29|2018-05-04|苹果公司|For abandoning equipment, method and the graphic user interface of generation tactile output for more contact gestures|

---

US20140187856A1|2012-12-31|2014-07-03|Lee D. Holoien|Control System For Modular Imaging Device|

---

US20150189425A1|2013-01-01|2015-07-02|Aliphcom|Mobile device speaker control|

---

US20150189426A1|2013-01-01|2015-07-02|Aliphcom|Mobile device speaker control|

---

KR102131646B1|2013-01-03|2020-07-08|삼성전자주식회사|Display apparatus and control method thereof|

---

US9183365B2|2013-01-04|2015-11-10|Synaptics Incorporated|Methods and systems for fingerprint template enrollment and distribution process|

---

US20140207659A1|2013-01-18|2014-07-24|Loop Commerce, Inc.|Recipient interface for a gift transaction system|

---

WO2014115605A1|2013-01-28|2014-07-31|インターナショナル・ビジネス・マシーンズ・コーポレーション|Method for propagating authentication state among plurality of terminals, and server and computer program thereof|

---

CN103067625A|2013-01-29|2013-04-24|周万荣|Calling and data transferring method, terminals and system|

---

CN103984494A|2013-02-07|2014-08-13|上海帛茂信息科技有限公司|System and method for intuitive user interaction among multiple pieces of equipment|

---

KR20140104215A|2013-02-20|2014-08-28|삼성전자주식회사|Wireless network audio system having auto pairing function and method of auto pairing using the same|

---

EP2770708B1|2013-02-22|2017-04-05|BlackBerry Limited|Device, system and method for generating application data|

---

US9830588B2|2013-02-26|2017-11-28|Digimarc Corporation|Methods and arrangements for smartphone payments|

---

US9710806B2|2013-02-27|2017-07-18|Fiserv, Inc.|Systems and methods for electronic payment instrument repository|

---

US9891662B2|2013-03-04|2018-02-13|Lg Electronics Inc.|Double unlocking apparatus of a portable device equipped with an expandable display and controlling method thereof|

---

US20140258292A1|2013-03-05|2014-09-11|Clip Interactive, Inc.|Apparatus, system, and method for integrating content and content services|

---

KR101443021B1|2013-03-08|2014-09-22|주식회사 슈프리마|Apparatus and method for registering face, and Apparatus for guiding pose, and Apparatus for recognizing face|

---

US20140257865A1|2013-03-10|2014-09-11|State Farm Mutual Automobile Insurance Company|Systems and methods for processing credits for distance-based insurance policies|

---

US20140279554A1|2013-03-12|2014-09-18|Seth Priebatsch|Distributed authenticity verification for consumer payment transactions|

---

US20140279497A1|2013-03-12|2014-09-18|Bank Of America Corporation|Secure Identity Element|

---

US20140279474A1|2013-03-12|2014-09-18|Visa International Service Association|Multi-purse one card transaction apparatuses, methods and systems|

---

US9319149B2|2013-03-13|2016-04-19|Aliphcom|Proximity-based control of media devices for media presentations|

---

FI20135248A|2013-03-14|2014-09-15|Op Palvelut Oy|Mobile device with transaction information|

---

US8924259B2|2013-03-14|2014-12-30|Square, Inc.|Mobile device payments|

---

US9179199B2|2013-03-14|2015-11-03|Apple Inc.|Media playback across multiple devices|

---

US9866924B2|2013-03-14|2018-01-09|Immersion Corporation|Systems and methods for enhanced television interaction|

---

US10219093B2|2013-03-14|2019-02-26|Michael Luna|Mono-spatial audio processing to provide spatial messaging|

---

US20140282240A1|2013-03-15|2014-09-18|William Joseph Flynn, III|Interactive Elements for Launching from a User Interface|

---

US20160028869A1|2013-03-15|2016-01-28|Apple Inc.|Providing remote interactions with host device using a wireless device|

---

US9183371B2|2013-03-15|2015-11-10|Tyfone, Inc.|Personal digital identity device with microphone|

---

WO2014143776A2|2013-03-15|2014-09-18|Bodhi Technology Ventures Llc|Providing remote interactions with host device using a wireless device|

---

US9400895B2|2013-03-15|2016-07-26|Intel Corporation|Mechanisms for locking computing devices|

---

US20140282103A1|2013-03-16|2014-09-18|Jerry Alan Crandall|Data sharing|

---

US8954611B2|2013-03-21|2015-02-10|Nextbit Systems Inc.|Mechanism for sharing states of applications and devices across different user profiles|

---

FI20135275A|2013-03-22|2014-09-23|Meontrust Oy|Transaction authorization method and system|

---

US10270748B2|2013-03-22|2019-04-23|Nok Nok Labs, Inc.|Advanced authentication techniques and applications|

---

WO2014157893A1|2013-03-27|2014-10-02|Samsung Electronics Co., Ltd.|Method and device for providing a private page|

---

JP6052004B2|2013-03-27|2016-12-27|富士通株式会社|Terminal device and terminal control program|

---

US9565181B2|2013-03-28|2017-02-07|Wendell D. Brown|Method and apparatus for automated password entry|

---

US9253375B2|2013-04-02|2016-02-02|Google Inc.|Camera obstruction detection|

---

US10027723B2|2013-04-12|2018-07-17|Provenance Asset Group Llc|Method and apparatus for initiating communication and sharing of content among a plurality of devices|

---

CN103260079A|2013-04-12|2013-08-21|深圳市龙视传媒有限公司|Control method and control device for multi-screen interaction|

---

US9247363B2|2013-04-16|2016-01-26|Sonos, Inc.|Playback queue transfer in a media playback system|

---

US20150193392A1|2013-04-17|2015-07-09|Google Inc.|User Interface for Quickly Checking Agenda and Creating New Events|

---

US9699295B2|2013-04-24|2017-07-04|Xiaomi Inc.|Method for displaying an icon and terminal device thereof|

---

US20140320387A1|2013-04-24|2014-10-30|Research In Motion Limited|Device, System and Method for Generating Display Data|

---

US9323455B2|2013-04-27|2016-04-26|Lg Electronics Inc.|Mobile terminal and method of controlling an external mobile terminal|

---

WO2014176749A1|2013-04-28|2014-11-06|Tencent Technology Company Limited|Method, device, server, and system for making payment with a messaging application on a mobile device|

---

US9591211B2|2013-05-10|2017-03-07|Huawei Technologies Co., Ltd.|Photographing method and apparatus|

---

US9104853B2|2013-05-16|2015-08-11|Symantec Corporation|Supporting proximity based security code transfer from mobile/tablet application to access device|

---

US10019710B2|2013-05-16|2018-07-10|Avant-Garde Ip Llc|System, method and article of manufacture to facilitate a financial transaction without unlocking a mobile device|

---

KR20140136350A|2013-05-20|2014-11-28|삼성전자주식회사|Method and apparatus for using a electronic device|

---

US9735978B2|2013-05-29|2017-08-15|Sonos, Inc.|Playback queue control via a playlist on a mobile device|

---

US9741177B2|2013-05-30|2017-08-22|Haroldo J. Montealegre|Transit fare collection system|

---

US20140359637A1|2013-06-03|2014-12-04|Microsoft Corporation|Task continuance across devices|

---

KR102124476B1|2013-06-03|2020-06-19|엘지전자 주식회사|Mobile terminal and method for controlling the same|

---

US9497231B2|2013-06-04|2016-11-15|Echostar Technologies L.L.C.|Real-time placeshifting of media content to paired devices|

---

US9294455B2|2013-06-04|2016-03-22|Google Inc.|Maintaining video conference session continuity during transfer of session to alternative device|

---

US9979438B2|2013-06-07|2018-05-22|Apple Inc.|Controlling a media device using a mobile device|

---

US9055210B2|2013-06-19|2015-06-09|Blackberry Limited|Device for detecting a camera obstruction|

---

TWI493437B|2013-06-19|2015-07-21|義隆電子股份有限公司|Method of opening window control bar by identification of edge swipe gesture and touch system using the method|

---

US9389691B2|2013-06-21|2016-07-12|Blackberry Limited|Devices and methods for establishing a communicative coupling in response to a gesture|

---

US20150006376A1|2013-06-27|2015-01-01|Ebay Inc.|Conductive payment device|

---

US20150006386A1|2013-06-28|2015-01-01|Sap Ag|Offline mobile payment process|

---

JP5654642B1|2013-07-05|2015-01-14|ソフトバンクモバイル株式会社|Authentication system and program|

---

US20150012417A1|2013-07-08|2015-01-08|Raymond Anthony Joao|Apparatus and method for providing transaction security and/or account security|

---

US20150012425A1|2013-07-08|2015-01-08|Mastercard International Incorporated|Intelligent advice and payment routing engine|

---

US9254633B2|2013-07-09|2016-02-09|Apple Inc.|Environmental seal maximizing sensor space beneath a button positioned in trim|

---

KR102065407B1|2013-07-11|2020-01-13|엘지전자 주식회사|Digital device amd method for controlling the same|

---

US20150019317A1|2013-07-13|2015-01-15|Spring Marketplace, Inc.|Systems and methods to enable offer and rewards marketing and CRM platform|

---

WO2015009111A1|2013-07-18|2015-01-22|삼성전자 주식회사|Biometrics-based authentication method and apparatus|

---

US9912978B2|2013-07-29|2018-03-06|Apple Inc.|Systems, methods, and computer-readable media for transitioning media playback between multiple electronic devices|

---

KR102127927B1|2013-07-30|2020-07-09|엘지전자 주식회사|Mobile terminal, smart watch and security authorizing method therbetween|

---

GB2516861A|2013-08-01|2015-02-11|Mastercard International Inc|Paired Wearable payment device|

---

CN103413218B|2013-08-07|2017-11-10|天地融科技股份有限公司|Mobile terminal, NFC payment, apparatus and system|

---

US20150046336A1|2013-08-09|2015-02-12|Mastercard International Incorporated|System and method of using a secondary screen on a mobile device as a secure and convenient transacting mechanism|

---

JP5541407B1|2013-08-09|2014-07-09|富士ゼロックス株式会社|Image processing apparatus and program|

---

JP2016535348A|2013-08-12|2016-11-10|ヒョンス パク|Electronic apparatus, control system, recording medium, and method using additional code|

---

US9948690B2|2013-08-15|2018-04-17|Comcast Cable Communications, Llc|Caching media in a media fling system|

---

US20150098309A1|2013-08-15|2015-04-09|I.Am.Plus, Llc|Multi-media wireless watch|

---

JP5705929B2|2013-08-16|2015-04-22|ファナック株式会社|Bearing life judgment device|

---

CN104426847A|2013-08-22|2015-03-18|腾讯科技（深圳）有限公司|Method, system and server for securely accessing and verifying an Internet service|

---

KR102090750B1|2013-08-23|2020-03-18|삼성전자주식회사|Electronic device and method for recognizing fingerprint|

---

US10346822B2|2013-08-23|2019-07-09|Visa International Service Association|Dynamic account selection|

---

US20150058191A1|2013-08-26|2015-02-26|Apple Inc.|Secure provisioning of credentials on an electronic device|

---

US20150066758A1|2013-08-27|2015-03-05|Richard DeNardis|Payment card systems and methods|

---

US9202029B2|2013-08-27|2015-12-01|Maan ALDUAIJI|Computer device, a method for controlling a login status of a computer device and a server|

---

US20150066762A1|2013-08-28|2015-03-05|Geoffrey W. Chatterton|Authentication system|

---

US9898642B2|2013-09-09|2018-02-20|Apple Inc.|Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs|

---

KR20150029495A|2013-09-10|2015-03-18|삼성전자주식회사|Method and apparatus for outputting recognized error of sensor in a electronic device|

---

KR102109617B1|2013-09-16|2020-05-13|주식회사 팬택|Terminal including fingerprint reader and method for processing a user input through the fingerprint reader|

---

US9654545B2|2013-09-30|2017-05-16|Sonos, Inc.|Group coordinator device selection|

---

US9288596B2|2013-09-30|2016-03-15|Sonos, Inc.|Coordinator device for paired or consolidated players|

---

JP2015075877A|2013-10-08|2015-04-20|シャープ株式会社|Imaging system|

---

US20150111559A1|2013-10-23|2015-04-23|Recurring Ventures LLC|System, method and article for managing mobile devices|

---

CN104579670A|2013-10-28|2015-04-29|腾讯科技（深圳）有限公司|Mobile terminal authentication method and mobile terminal|

---

GB2519766A|2013-10-29|2015-05-06|Mastercard International Inc|A system and method for disseminating functionality to a target device|

---

KR102091606B1|2013-10-30|2020-03-20|엘지전자 주식회사|Terminal and method for controlling the same|

---

WO2015065125A1|2013-10-31|2015-05-07|엘지전자|Electronic device and method for controlling electronic device|

---

US20150127550A1|2013-11-04|2015-05-07|Apple Inc.|Using bioauthentication in near-field-communication transactions|

---

US10528946B2|2013-11-06|2020-01-07|Tencent Technology Company Limited|System and method for authenticating, associating and storing secure information|

---

CN103558916A|2013-11-07|2014-02-05|百度在线网络技术（北京）有限公司|Man-machine interaction system, method and device|

---

JP5920894B2|2013-11-07|2016-05-18|株式会社ソニー・インタラクティブエンタテインメント|Information processing apparatus and face identification data registration method|

---

US10110932B2|2013-11-18|2018-10-23|Cable Television Laboratories, Inc.|Session administration|

---

EP3072315B1|2013-11-22|2021-11-03|Apple Inc.|Handsfree beam pattern configuration|

---

US8738723B1|2013-12-10|2014-05-27|Google Inc.|Predictive forwarding of notification data|

---

TW201527631A|2013-12-20|2015-07-16|Jetdian Technology Inc|Locking/unlocking method adopting near field wireless transmission device|

---

US9319782B1|2013-12-20|2016-04-19|Amazon Technologies, Inc.|Distributed speaker synchronization|

---

US20160314290A1|2013-12-23|2016-10-27|Intel Corporation|Computing device authentication based on user's hair follicle pattern|

---

CN103701605A|2013-12-24|2014-04-02|北京握奇智能科技有限公司|Data authentication method and device|

---

US9811870B2|2013-12-24|2017-11-07|Tencent Technology Company Limited|Information processing method, apparatus and payment system|

---

WO2015097829A1|2013-12-26|2015-07-02|株式会社東芝|Method, electronic device and program|

---

US20150186152A1|2013-12-27|2015-07-02|Gangatharan Jothiswaran|Sensing and assisting computing device connections|

---

US9684778B2|2013-12-28|2017-06-20|Intel Corporation|Extending user authentication across a trust group of smart devices|

---

CN105940678A|2013-12-30|2016-09-14|汤姆逊许可公司|Proximity dependent media playback|

---

US20150186892A1|2013-12-30|2015-07-02|Tencent Technology Company Limited|Methods and systems for verifying a transaction|

---

US20150187019A1|2013-12-31|2015-07-02|Hartford Fire Insurance Company|Systems and method for autonomous vehicle data processing|

---

KR101569268B1|2014-01-02|2015-11-13|아이리텍 잉크|Acquisition System and Method of Iris image for iris recognition by using facial component distance|

---

US20150193069A1|2014-01-03|2015-07-09|Harman International Industries, Incorporated|Seamless content transfer|

---

US9514748B2|2014-01-15|2016-12-06|Microsoft Technology Licensing, Llc|Digital personal assistant interaction with impersonations and rich multimedia in responses|

---

JP6255109B2|2014-01-23|2017-12-27|アップル インコーポレイテッド|System, program and method for dynamically providing user interface control in a touch sensitive secondary display|

---

US9369282B2|2014-01-29|2016-06-14|Red Hat, Inc.|Mobile device user authentication for accessing protected network resources|

---

US9223955B2|2014-01-30|2015-12-29|Microsoft Corporation|User-authentication gestures|

---

US20150220924A1|2014-02-04|2015-08-06|Outsite Networks, Inc.|Method and system for linking a customer identity to a retail transaction|

---

US9208301B2|2014-02-07|2015-12-08|Bank Of America Corporation|Determining user authentication requirements based on the current location of the user in comparison to the users's normal boundary of location|

---

US9185117B2|2014-02-07|2015-11-10|Bank Of America Corporation|User authentication by geo-location and proximity to user's close network|

---

US20160012465A1|2014-02-08|2016-01-14|Jeffrey A. Sharp|System and method for distributing, receiving, and using funds or credits and apparatus thereof|

---

WO2015120019A1|2014-02-10|2015-08-13|Google Inc.|Smart camera user interface|

---

US9311639B2|2014-02-11|2016-04-12|Digimarc Corporation|Methods, apparatus and arrangements for device to device communication|

---

US9569605B1|2014-02-12|2017-02-14|Symantec Corporation|Systems and methods for enabling biometric authentication options|

---

EP2911149B1|2014-02-19|2019-04-17|Nokia Technologies OY|Determination of an operational directive based at least in part on a spatial audio property|

---

KR102204247B1|2014-02-19|2021-01-18|삼성전자 주식회사|Apparatus and Method for processing biometric information in a electronic device|

---

US20150242597A1|2014-02-24|2015-08-27|Google Inc.|Transferring authorization from an authenticated device to an unauthenticated device|

---

US9408008B2|2014-02-28|2016-08-02|Sonos, Inc.|Playback zone representations|

---

US9537661B2|2014-02-28|2017-01-03|Verizon Patent And Licensing Inc.|Password-less authentication service|

---

US9679054B2|2014-03-05|2017-06-13|Sonos, Inc.|Webpage media playback|

---

US9503894B2|2014-03-07|2016-11-22|Cellco Partnership|Symbiotic biometric security|

---

EP3118761B1|2014-03-13|2021-05-12|LG Electronics Inc.|Mobile terminal and method for controlling same|

---

US9450812B2|2014-03-14|2016-09-20|Dechnia, LLC|Remote system configuration via modulated audio|

---

US9722962B2|2014-03-21|2017-08-01|Facebook, Inc.|Providing message status notifications during electronic messaging|

---

JP6287450B2|2014-03-26|2018-03-07|富士通株式会社|Portable information processing apparatus and program|

---

US20150278799A1|2014-03-27|2015-10-01|Karthikeyan Palanisamy|System incorporating wireless share process|

---

JP2014131359A|2014-04-07|2014-07-10|Dainippon Printing Co Ltd|Terminal device, mobile telephone apparatus, operation management method, operation management program, and the like|

---

US20150286694A1|2014-04-08|2015-10-08|International Business Machines Corporation|Integrating a mobile payment application with other applications utilizing analytic analysis|

---

CN105099673A|2014-04-15|2015-11-25|阿里巴巴集团控股有限公司|Authorization method, authorization requesting method and devices|

---

US10438276B2|2014-04-16|2019-10-08|Ebay Inc.|Smart recurrent orders|

---

US20150302493A1|2014-04-16|2015-10-22|LuvTap|Interactive transactions|

---

US20150302856A1|2014-04-17|2015-10-22|Qualcomm Incorporated|Method and apparatus for performing function by speech input|

---

US9680960B2|2014-04-28|2017-06-13|Sonos, Inc.|Receiving media content based on media preferences of multiple users|

---

US10129599B2|2014-04-28|2018-11-13|Sonos, Inc.|Media preference database|

---

US9679121B2|2014-05-06|2017-06-13|International Business Machines Corporation|Unlocking electronic devices using touchscreen input gestures|

---

JP2015215687A|2014-05-08|2015-12-03|パナソニックＩｐマネジメント株式会社|Portable settlement terminal device|

---

NZ725355A|2014-05-08|2018-05-25|Thumbzup Uk Ltd|Authentication code entry system and method|

---

US9408076B2|2014-05-14|2016-08-02|The Regents Of The University Of California|Sensor-assisted biometric authentication for smartphones|

---

KR102185702B1|2014-05-16|2020-12-02|삼성전자주식회사|Contents output apparatus, mobile apparatus and controlling method thereof|

---

CN104038256A|2014-05-28|2014-09-10|南京邮电大学|NFC transmission method based on biometric feature recognition|

---

US9483763B2|2014-05-29|2016-11-01|Apple Inc.|User interface for payments|

---

US9400977B2|2014-05-29|2016-07-26|Apple Inc.|User device enabling access to payment information in response to mechanical input detection|

---

CN110807631A|2014-05-29|2020-02-18|苹果公司|User interface for payments|

---

US9967401B2|2014-05-30|2018-05-08|Apple Inc.|User interface for phone call routing among devices|

---

JP6328797B2|2014-05-30|2018-05-23|アップル インコーポレイテッド|Transition from using one device to using another device|

---

US10318016B2|2014-06-03|2019-06-11|Harman International Industries, Incorporated|Hands free device with directional interface|

---

US9654459B2|2014-06-04|2017-05-16|Sonos, Inc.|Cloud queue synchronization protocol|

---

US9424417B2|2014-06-04|2016-08-23|Qualcomm Incorporated|Secure current movement indicator|

---

US9264423B2|2014-06-12|2016-02-16|Nadapass, Inc.|Password-less authentication system and method|

---

US9349035B1|2014-06-13|2016-05-24|Maxim Integrated Products, Inc.|Multi-factor authentication sensor for providing improved identification|

---

EP3057074B1|2014-06-13|2017-08-09|Huawei Technologies Co., Ltd.|Controlled device selecting method and control device|

---

KR102236279B1|2014-06-17|2021-04-02|엘지전자 주식회사|Mobile terminal and method for controlling the same|

---

US9084003B1|2014-06-19|2015-07-14|Google Inc.|Methods, systems, and media for media playback|

---

US9817549B2|2014-06-25|2017-11-14|Verizon Patent And Licensing Inc.|Method and system for auto switching applications based on device orientation|

---

US9535986B2|2014-06-27|2017-01-03|Sonos, Inc.|Application launch|

---

US20160005028A1|2014-07-07|2016-01-07|Verizon Patent And Licensing Inc.|Systems and Methods for Providing Gifts Via a Mobile Messaging Platform|

---

US9671997B2|2014-07-23|2017-06-06|Sonos, Inc.|Zone grouping|

---

KR101773233B1|2014-07-25|2017-09-12|이동광|Managing method for repeating fail of biometric recognition|

---

WO2016018028A1|2014-07-31|2016-02-04|Samsung Electronics Co., Ltd.|Device and method of setting or removing security on content|

---

US10339293B2|2014-08-15|2019-07-02|Apple Inc.|Authenticated device used to unlock another device|

---

US10621670B2|2014-08-15|2020-04-14|Scope Technologies Holdings Limited|Determination and display of driving risk|

---

JP6044604B2|2014-08-18|2016-12-14|カシオ計算機株式会社|Terminal device and program|

---

CA2902093A1|2014-08-28|2016-02-28|Kevin Alan Tussy|Facial recognition authentication system including path parameters|

---

WO2016033400A1|2014-08-29|2016-03-03|Harman International Industries, Inc.|Wireless speaker system|

---

US9465930B2|2014-08-29|2016-10-11|Dropbox, Inc.|Fingerprint gestures|

---

US10275138B2|2014-09-02|2019-04-30|Sonos, Inc.|Zone recognition|

---

US10089607B2|2014-09-02|2018-10-02|Apple Inc.|Mobile merchant proximity solution for financial transactions|

---

JP2016053766A|2014-09-02|2016-04-14|株式会社バンダイナムコエンターテインメント|Charge system for virtual currency, and program|

---

US20160092877A1|2014-09-25|2016-03-31|Yen Hsiang Chew|Secure user authentication interface technologies|

---

US20160092665A1|2014-09-27|2016-03-31|Intel Corporation|Liveness Detection for User Authentication|

---

JP6567261B2|2014-09-30|2019-08-28|Kddi株式会社|Electronic currency management apparatus, electronic currency management method, and electronic currency management system|

---

US9269083B1|2014-09-30|2016-02-23|Wal-Mart Stores, Inc.|Mobile device payment|

---

WO2016052876A1|2014-09-30|2016-04-07|Samsung Electronics Co., Ltd.|Display apparatus and controlling method thereof|

---

US20160104228A1|2014-10-14|2016-04-14|Ebay Inc.|Bottomless inventory interface|

---

CN104361302B|2014-10-21|2017-10-17|天津三星电子有限公司|The method and communication apparatus of a kind of protection privacy information based on communication apparatus|

---

CN104460593B|2014-10-29|2017-10-10|小米科技有限责任公司|mode switching method and device|

---

CN105657483B|2014-11-10|2019-06-04|扬智科技股份有限公司|Multimedia play system, multimedia file sharing method and its control method|

---

US10027667B2|2014-11-12|2018-07-17|Time Warner Cable Enterprises Llc|Methods and apparatus for provisioning services which require a device to be securely associated with an account|

---

US9412169B2|2014-11-21|2016-08-09|iProov|Real-time visual feedback for user positioning with respect to a camera and a display|

---

RU2707874C2|2014-11-25|2019-12-02|Филипс Лайтинг Холдинг Б.В.|Lighting control based on proximity|

---

CN104539924A|2014-12-03|2015-04-22|深圳市亿思达科技集团有限公司|Holographic display method and holographic display device based on eye tracking|

---

US10223689B2|2014-12-10|2019-03-05|American Express Travel Related Services Company, Inc.|System and method for over the air provisioned wearable contactless payments|

---

US9912758B2|2014-12-16|2018-03-06|Yahoo Holdings, Inc.|Continuing an application session on a different device|

---

KR101714349B1|2014-12-29|2017-03-09|주식회사 슈프리마|Biometric image output-control method and biometric authentification apparatus|

---

US10111093B2|2015-01-09|2018-10-23|Qualcomm Incorporated|Mobile device to provide continuous and discrete user authentication|

---

US10037528B2|2015-01-14|2018-07-31|Tactilis Sdn Bhd|Biometric device utilizing finger sequence for authentication|

---

US20160210623A1|2015-01-15|2016-07-21|Ebay Inc.|Pre-authorized device for shopping experience|

---

US20160224973A1|2015-02-01|2016-08-04|Apple Inc.|User interface for payments|

---

US9654978B2|2015-02-03|2017-05-16|Qualcomm Incorporated|Asset accessibility with continuous authentication for mobile devices|

---

US20160232516A1|2015-02-06|2016-08-11|Google Inc.|Predictive authorization of mobile payments|

---

KR20160099397A|2015-02-12|2016-08-22|삼성전자주식회사|Method and Apparatus for Performing Payment Function in Limited State|

---

KR102338864B1|2015-02-12|2021-12-13|삼성전자주식회사|Electronic device and method for registration finger print|

---

US9305155B1|2015-02-12|2016-04-05|United Services Automobile Association |Toggling biometric authentication|

---

KR20160105261A|2015-02-27|2016-09-06|삼성전자주식회사|Method and apparatus for providing card service using electronic device|

---

US10567477B2|2015-03-08|2020-02-18|Apple Inc.|Virtual assistant continuity|

---

WO2016149208A1|2015-03-17|2016-09-22|Microsoft Technology Licensing, Llc|Selectively providing personal information and access to functionality on lock screen based on biometric user authentication|

---

JP2016194799A|2015-03-31|2016-11-17|富士通株式会社|Image analyzer and image analysis method|

---

US9891880B2|2015-03-31|2018-02-13|Sonos, Inc.|Information display regarding playback queue subscriptions|

---

US9779585B2|2015-03-31|2017-10-03|Igt Canada Solutions Ulc|Multi-touch user interface for scaling reward value with random failure threshold for gaming system|

---

US9774453B2|2015-04-01|2017-09-26|Northrop Grumman Systems Corporation|System and method for providing an automated biometric enrollment workflow|

---

JP5920747B1|2015-04-07|2016-05-18|エイピーエス．エスエイ|Application programs and cards|

---

US10305895B2|2015-04-14|2019-05-28|Blubox Security, Inc.|Multi-factor and multi-mode biometric physical access control device|

---

US10319203B1|2015-04-15|2019-06-11|Cellotape, Inc.|Track and trace device, systems and methods thereof|

---

US10776769B2|2015-04-27|2020-09-15|Hrb Innovations, Inc.|Unified payment vehicle|

---

KR20160141566A|2015-06-01|2016-12-09|엘지전자 주식회사|Mobile terminal and control method for the mobile terminal|

---

KR20160143136A|2015-06-04|2016-12-14|엘지전자 주식회사|Location based reminder system and method for controlling the same|

---

US20160358133A1|2015-06-05|2016-12-08|Apple Inc.|User interface for loyalty accounts and private label accounts for a wearable device|

---

US9940637B2|2015-06-05|2018-04-10|Apple Inc.|User interface for loyalty accounts and private label accounts|

---

US20160364600A1|2015-06-10|2016-12-15|Microsoft Technology Licensing, Llc|Biometric Gestures|

---

US20160364591A1|2015-06-15|2016-12-15|Cypress Semiconductor Corporation|Fingerprint Sensing Access for Security and Personalization in Apps and Devices|

---

JP6140773B2|2015-06-26|2017-05-31|京セラ株式会社|Electronic device and method of operating electronic device|

---

US10094655B2|2015-07-15|2018-10-09|15 Seconds of Fame, Inc.|Apparatus and methods for facial recognition and video analytics to identify individuals in contextual video streams|

---

CN105187940B|2015-07-29|2018-05-29|广东欧珀移动通信有限公司|The playlist method for handover control and device of a kind of play system|

---

KR101696602B1|2015-08-11|2017-01-23|주식회사 슈프리마|Biometric authentication using gesture|

---

US10708396B2|2015-08-20|2020-07-07|Lg Electronics Inc.|Mobile terminal having card unit and method for controlling same|

---

KR20170025802A|2015-08-31|2017-03-08|삼성전자주식회사|Method and apparatus for authentication based on fingerprint recognition|

---

KR20170027999A|2015-09-03|2017-03-13|삼성전자주식회사|User terminal apparatus, system and the controlling method thereof|

---

US9628275B2|2015-09-04|2017-04-18|Blackberry Limited|Communication device, method and system for establishing communications using the subscriber identity data of another communication device|

---

US10120531B2|2015-09-08|2018-11-06|Apple Inc.|User interfaces for navigating and playing content|

---

JP6613740B2|2015-09-09|2019-12-04|富士通コネクテッドテクノロジーズ株式会社|Display control apparatus, display control method, and display control program|

---

US10257198B2|2015-09-11|2019-04-09|Arris Enterprises Llc|Password input method for devices with limited user interface|

---

US9519901B1|2015-09-16|2016-12-13|Square, Inc.|Biometric payment technology|

---

KR20170033641A|2015-09-17|2017-03-27|삼성전자주식회사|Electronic device and method for controlling an operation thereof|

---

US9558636B1|2015-09-28|2017-01-31|Uniloc Luxembourg S.A.|Automatic teller machine inventory and distribution system|

---

US20170092270A1|2015-09-30|2017-03-30|Apple Inc.|Intelligent device identification|

---

CN108028787B|2015-09-30|2021-01-12|苹果公司|Coordinated control of media playback|

---

KR20170048990A|2015-10-27|2017-05-10|엘지전자 주식회사|Watch-type mobile terminal and operating method thereof|

---

CN105320864A|2015-10-28|2016-02-10|广东欧珀移动通信有限公司|Method and apparatus for processing event operation|

---

US20180260108A1|2015-11-23|2018-09-13|Verifone, Inc.|Systems and methods for authentication code entry in touch-sensitive screen enabled devices|

---

US10275115B2|2015-11-25|2019-04-30|Verizon Patent And Licensing Inc.|Multifunction icon for user feedback including context information|

---

US10210318B2|2015-12-09|2019-02-19|Daon Holdings Limited|Methods and systems for capturing biometric data|

---

US10003738B2|2015-12-18|2018-06-19|Light Labs Inc.|Methods and apparatus for detecting and/or indicating a blocked sensor or camera module|

---

CN105549947B|2015-12-21|2019-03-29|联想有限公司|A kind of control method and electronic equipment of audio frequency apparatus|

---

KR20170074552A|2015-12-22|2017-06-30|삼성전자주식회사|Speaker device comprising touch display|

---

US10102358B2|2015-12-29|2018-10-16|Sensory, Incorporated|Face-controlled liveness verification|

---

KR20170081508A|2016-01-04|2017-07-12|삼성전자주식회사|Electronic apparatus and operating method thereof|

---

US10284980B1|2016-01-05|2019-05-07|Sonos, Inc.|Intelligent group identification|

---

CN105787718A|2016-02-03|2016-07-20|浙江万里学院|Business logistics safe payment method based on cash on delivery|

---

JP2017138846A|2016-02-04|2017-08-10|レノボ・シンガポール・プライベート・リミテッド|Information processing apparatus, display method by the same, and computer-executable program|

---

US9898250B1|2016-02-12|2018-02-20|Amazon Technologies, Inc.|Controlling distributed audio outputs to enable voice output|

---

KR20170098096A|2016-02-19|2017-08-29|삼성전자주식회사|Method and apparatus for connectiong between electronic devices using authentication based on biometric information|

---

CN105844468A|2016-03-17|2016-08-10|上海新储集成电路有限公司|Mobile-terminal ultra-low power consumption and high safety communication method|

---

US10019904B1|2016-04-11|2018-07-10|State Farm Mutual Automobile Insurance Company|System for identifying high risk parking lots|

---

US20170300897A1|2016-04-14|2017-10-19|American Express Travel Related Services Company, Inc.|Systems and Methods for an Electronic Wallet Payment Tool|

---

DK179186B1|2016-05-19|2018-01-15|Apple Inc|REMOTE AUTHORIZATION TO CONTINUE WITH AN ACTION|

---

CN105868613A|2016-06-08|2016-08-17|广东欧珀移动通信有限公司|Biometric feature recognition method, biometric feature recognition device and mobile terminal|

---

US10621581B2|2016-06-11|2020-04-14|Apple Inc.|User interface for transactions|

---

US9716825B1|2016-06-12|2017-07-25|Apple Inc.|User interface for camera effects|

---

WO2017218094A1|2016-06-12|2017-12-21|Apple Inc.|User interfaces for transactions|

---

AU2017100556B4|2016-06-12|2017-10-05|Apple Inc.|User interfaces for transactions|

---

US20180004924A1|2016-06-30|2018-01-04|Synaptics Incorporated|Systems and methods for detecting biometric template aging|

---

US10265856B2|2016-07-21|2019-04-23|X Development Llc|Reorienting a distance sensor using an adjustable leveler|

---

CN106156566A|2016-07-29|2016-11-23|努比亚技术有限公司|implicit authentication apparatus and method|

---

US9842330B1|2016-09-06|2017-12-12|Apple Inc.|User interfaces for stored-value accounts|

---

CN106355058A|2016-09-13|2017-01-25|珠海格力电器股份有限公司|Terminal unlocking method and device|

---

US9794720B1|2016-09-22|2017-10-17|Sonos, Inc.|Acoustic position measurement|

---

CN106503514A|2016-09-28|2017-03-15|北京用友政务软件有限公司|Unlocking method and system based on the electric terminal equipment of iris identification|

---

CN106485123A|2016-10-17|2017-03-08|信利光电股份有限公司|A kind of cold screen awakening method and intelligent terminal|

---

US9739627B1|2016-10-18|2017-08-22|Allstate Insurance Company|Road frustration index risk mapping and mitigation|

---

US10496808B2|2016-10-25|2019-12-03|Apple Inc.|User interface for managing access to credentials for use in an operation|

---

CN106383645A|2016-10-31|2017-02-08|维沃移动通信有限公司|Music playing control method and mobile terminal|

---

CN106778222B|2016-12-20|2020-06-02|北京小米移动软件有限公司|Unlocking method and device|

---

US10992795B2|2017-05-16|2021-04-27|Apple Inc.|Methods and interfaces for home media control|

---

EP3593538B1|2017-05-16|2021-12-08|Apple Inc.|Credential delegation|

---

US11201961B2|2017-05-16|2021-12-14|Apple Inc.|Methods and interfaces for adjusting the volume of media|

---

WO2018226265A1|2017-09-09|2018-12-13|Apple Inc.|Implementation of biometric authentication|

---

KR20200136504A|2017-09-09|2020-12-07|애플 인크.|Implementation of biometric authentication|

---

KR102301599B1|2017-09-09|2021-09-10|애플 인크.|Implementation of biometric authentication|

---

CN109769397A|2017-09-09|2019-05-17|苹果公司|The realization of biometric authentication|

---

US10466962B2|2017-09-29|2019-11-05|Sonos, Inc.|Media playback system with voice assistance|

---

US11170085B2|2018-06-03|2021-11-09|Apple Inc.|Implementation of biometric authentication|

---

WO2020243691A1|2019-05-31|2020-12-03|Apple Inc.|User interfaces for audio media control|

---

US10996917B2|2019-05-31|2021-05-04|Apple Inc.|User interfaces for audio media control|US8769624B2|2011-09-29|2014-07-01|Apple Inc.|Access control utilizing indirect authentication|

---

US9002322B2|2011-09-29|2015-04-07|Apple Inc.|Authentication with secondary approver|

---

US9483763B2|2014-05-29|2016-11-01|Apple Inc.|User interface for payments|

---

US9967401B2|2014-05-30|2018-05-08|Apple Inc.|User interface for phone call routing among devices|

---

US10339293B2|2014-08-15|2019-07-02|Apple Inc.|Authenticated device used to unlock another device|

---

US10299216B1|2018-01-06|2019-05-21|Eric John Wengreen|Self-driving vehicle actions in response to a low battery|

---

US11073838B2|2018-01-06|2021-07-27|Drivent Llc|Self-driving vehicle systems and methods|

---

DK179186B1|2016-05-19|2018-01-15|Apple Inc|REMOTE AUTHORIZATION TO CONTINUE WITH AN ACTION|

---

US9842330B1|2016-09-06|2017-12-12|Apple Inc.|User interfaces for stored-value accounts|

---

US10496808B2|2016-10-25|2019-12-03|Apple Inc.|User interface for managing access to credentials for use in an operation|

---

US10679201B2|2016-11-04|2020-06-09|Nxp B.V.|Personal point of saledevice that provides for card present E-commerce transaction|

---

US10992795B2|2017-05-16|2021-04-27|Apple Inc.|Methods and interfaces for home media control|

---

US11201961B2|2017-05-16|2021-12-14|Apple Inc.|Methods and interfaces for adjusting the volume of media|

---

KR102301599B1|2017-09-09|2021-09-10|애플 인크.|Implementation of biometric authentication|

---

KR20200136504A|2017-09-09|2020-12-07|애플 인크.|Implementation of biometric authentication|

---

US10607231B1|2017-09-27|2020-03-31|Worldpay, Llc|Systems and methods for optimizing transaction authorization conversion rate|

---

EP3441923A1|2017-12-01|2019-02-13|Barclays Bank Plc.|Facilitating a location-specific transaction|

---

US11023897B1|2017-12-05|2021-06-01|Worldpay, Llc|Systems and methods for optimizing transaction conversion rate using measured feedback|

---

JP2019168890A|2018-03-23|2019-10-03|カシオ計算機株式会社|Electronic terminal, electronic timepiece, security setting method, and program|

---

US11170085B2|2018-06-03|2021-11-09|Apple Inc.|Implementation of biometric authentication|

---

US10794714B2|2018-10-01|2020-10-06|Drivent Llc|Self-driving vehicle systems and methods|

---

US10471804B1|2018-09-18|2019-11-12|Drivent Llc|Self-driving vehicle systems and methods|

---

US10282625B1|2018-10-01|2019-05-07|Eric John Wengreen|Self-driving vehicle systems and methods|

---

US10493952B1|2019-03-21|2019-12-03|Drivent Llc|Self-driving vehicle systems and methods|

---

US10479319B1|2019-03-21|2019-11-19|Drivent Llc|Self-driving vehicle systems and methods|

---

US10900792B2|2018-10-22|2021-01-26|Drivent Llc|Self-driving vehicle systems and methods|

---

US10832569B2|2019-04-02|2020-11-10|Drivent Llc|Vehicle detection systems|

---

US10474154B1|2018-11-01|2019-11-12|Drivent Llc|Self-driving vehicle systems and methods|

---

US10303181B1|2018-11-29|2019-05-28|Eric John Wengreen|Self-driving vehicle systems and methods|

---

US10637942B1|2018-12-05|2020-04-28|Citrix Systems, Inc.|Providing most recent application views from user devices|

---

WO2020152709A1|2019-01-24|2020-07-30|Vibhor Jain|System and method for switching/reversing between payment modes and managing user transactions thereof|

---

US10963347B1|2019-01-31|2021-03-30|Splunk Inc.|Data snapshots for configurable screen on a wearable device|

---

US10744976B1|2019-02-04|2020-08-18|Drivent Llc|Self-driving vehicle systems and methods|

---

US10377342B1|2019-02-04|2019-08-13|Drivent Technologies Inc.|Self-driving vehicle systems and methods|

---

US11221622B2|2019-03-21|2022-01-11|Drivent Llc|Self-driving vehicle systems and methods|

---

US10996917B2|2019-05-31|2021-05-04|Apple Inc.|User interfaces for audio media control|

法律状态:
2019-07-12| PHB| Application deemed withdrawn due to non-payment or other reasons|Effective date: 20190618 |

优先权:

---

申请号 | 申请日 | 专利标题

---

US201662349010P| true| 2016-06-12|2016-06-12|CN201780033899.9A| CN109219827A|2016-06-12|2017-05-04|User interface for transaction|

---

EP17813737.8A| EP3469536A4|2016-06-12|2017-05-04|User interfaces for transactions|

---

PCT/US2017/031086| WO2017218094A1|2016-06-12|2017-05-04|User interfaces for transactions|

---

AU2017284013A| AU2017284013B2|2016-06-12|2017-05-04|User interfaces for transactions|

---

AU2017100556A| AU2017100556B4|2016-06-12|2017-05-17|User interfaces for transactions|

---

AU2017101563A| AU2017101563A4|2016-06-12|2017-11-03|User interfaces for transactions|

---

AU2018101014A| AU2018101014C4|2016-06-12|2018-07-23|User interfaces for transactions|

---

AU2020273355A| AU2020273355B2|2016-06-12|2020-11-20|User interfaces for transactions|